Gossamer Forum
Home : Products : Gossamer Links : Development, Plugins and Globals :

Bad_link.cgi problem

(Page 1 of 2)
> >
Quote Reply
Bad_link.cgi problem
I installed the newest version of this plug-in (v2.1.0) and can't seem to get it to work properly even after setting the permissions to chmod 755. I keep getting the File Download box where it asks you if you want to "open this file from its current location" or to "save this file to disk."

I had v.2.0.5 previously and it worked without a hitch.

Please advise!

Thanks a lot.


Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
Here's what I get when attempting to download the file:

http://www.ohiobiz.com/linkssql2/pages/links.css Unknown Tag: 'body_tag'
Unknown Tag: 'body_table' Error: Can't load included file: '/home2/www/ohiobiz/linkssql2/admin/templates/default/menu.txt'. Reason: No such file or directory Error: Can't load included file: '/home2/www/ohiobiz/linkssql2/admin/templates/default/search_bar.htm'. Reason: No such file or directory Unknown Tag: 'header_row' Unknown Tag: 'body_font'Thank you for taking the time to report the following link as bad:
Unknown Tag: 'body_font'Title: Toledo, Ohio from About.com
Unknown Tag: 'body_font'URL: http://toledo.about.com/
Unknown Tag: 'body_font'Description: Toledo/Lucas County - A valuable resource of hundreds of Toledo area Internet resources, feature articles, and timely information.





Error: Can't load included file: '/home2/www/ohiobiz/linkssql2/admin/templates/default/menu.txt'. Reason: No such file or directory


Can anyone make "heads or tails" of this problem I have with the Bad Link plugin?

Thanks in advance!

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
Hi,

I believe the "version" info says this works with Links 2.04 or above.

If you need a version that works with 2.03 or below, email me.

If you are running 2.04, then you need to EDIT THE TEMPLATE!!! (which you should really do anyway!) and get rid of the extra tags you don't need.

I switched to the new default layout, since that is what most people will be installing, and menu.txt, body_font, body_table, etc are all new tags in the 2.04 globals.txt file.



PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
Hello,

I edited the Bad link template (bad_link.html) and took care of that problem but I still have an issue with the File Download box popping up whenever you click on any of the "Report A Broken LinK" links within in my site. I doublechecked the permissions (chmod 755) as well.

Feel free to take a look - http://www.ohiobiz.com/linkssql2/page.cgi and then just go to any category link and click on the "Report A Broken Link" link.

I just am scratching my head on this one!

Thanks in advance.

MArk G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
I can't figure that out either. It works on my servers, and every where it returns a template, it has a print $IN->header(); right before it.

Can you turn "compress off" in your admin, maybe something else is going on.

PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
I uninstalled, then deleted, the Bad link plugin, turned off the compress mode in the Admin and then re-downloaded and re-installed the plugin and still get the File Download box!

Help!

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
Code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html>

<head>
<title>Gossamer Threads Inc.: BAD LINK REPORTED</title>
http://www.ohiobiz.com/linkssql2/pages/links.css
</head>

Unknown Tag: 'body_tag'
<center>
Unknown Tag: 'body_table'
It might be because you don't have a "body" tag, and the header line
is telling the browser what to look for. Delete the <!DOCTYP...> line from the template and see if that makes a difference.

If that doesn't, then try adding a <BODY> tag after the head tag.

PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
Actually, it's probably:

http://www.ohiobiz.com/linkssql2/pages/links.css


That gives a "file not found error" and when the .css file is missing, very strange things happen.

PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
There is a link.css file in that location. I tried the other suggestions listed above to no avail.

Thanks.

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
I mean links.css file.

Sorry.

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
Save the template to your local pc as text, then transfer it back to the server as ASCII. There are some binary characters in it, near the top, that might be causing the problem.

PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
I just tried that and I'm still getting that file Download box when clicking on the link!

Would like to get access to the site to see where the problem might be?

Thanks.

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
Would this be a possible cause of the probelem? I found this information when doing a perl check on the bad_link.html file (Plugin Files):

Perl Said:


Unquoted string "html" may clash with future reserved word at bad_link.html line 2.
syntax error at bad_link.html line 2, near "html>"
Unquoted string "title" may clash with future reserved word at bad_link.html line 5.
Bareword found where operator expected at bad_link.html line 7, near "> string starting on line 13)
(Missing operator before menu?)
Unquoted string "menu" may clash with future reserved word at bad_link.html line 15.
Unquoted string "txt" may clash with future reserved word at bad_link.html line 15.
Bareword found where operator expected at bad_link.html line 20, near "0 width"
(Might be a runaway multi-line >> string starting on line 18)
(Missing operator before width?)
Unquoted string "width" may clash with future reserved word at bad_link.html line 20.
Bareword found where operator expected at bad_link.html line 20, near ""100%" cellpadding"
(Missing operator before cellpadding?)
Unquoted string "cellpadding" may clash with future reserved word at bad_link.html line 20.
Bareword found where operator expected at bad_link.html line 20, near "0 cellspacing"
(Missing operator before cellspacing?)
Unquoted string "cellspacing" may clash with future reserved word at bad_link.html line 20.
Bareword found where operator expected at bad_link.html line 22, near "6 rowspan"
(Missing operator before rowspan?)
Unquoted string "rowspan" may clash with future reserved word at bad_link.html line 22.
Bareword found where operator expected at bad_link.html line 30, near "BAD LINK REPORTED!Thank"
(Missing operator before Thank?)
Missing $ on loop variable at bad_link.html line 49.

Thanks.

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
You can't really perl check an html file :)

PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
I went back to v.2.0.5 and it seems to work fine, again - so I'll just live with that version.

Thanks for all of your assistance.

Mark G.
OhioBiz

Quote Reply
Re: Bad_link.cgi problem In reply to
I'm still trying to swat this one, but it seems this is the only report of it's kind.



PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: Bad_link.cgi problem In reply to
Hi pugdog,

I have a similar problem with your plugin (2.1.0 and LSQL 2.04), only that I'm not getting the download box but instead I get the HTML output as source code.

I tried with the unchanged template which was installed and also with a customized one, without the DOCTYPE statement. I also have a BODY tag in the template and a css file is located where it is expected. So it doesn't seem to be a problem with the template itself...
(oh, I also tried with some different permissions - all the same error)

Andreas
http://www.archaeologie-online.de
Quote Reply
Re: Bad_link.cgi problem In reply to
I can't duplicate this.

Are you running under Unix or NT/2000??


PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Plugins:http://LinkSQL.com/plugin
Quote Reply
Re: Bad_link.cgi problem In reply to
I'm running under Unix (Linux).

You can try this URL for testing:
http://212.227.253.138/...bad_link.cgi?ID=2167

The output will be the source of the template.
There will be also some unknown tag messages because I haven't switched to the new template set completely for now.

Andreas
http://www.archaeologie-online.de
Quote Reply
Re: Bad_link.cgi problem In reply to
i have the same problem. a download-box opens and if you open it, you just get the source of the template file.


Manu

http://www.shop-netz.com
Quote Reply
Re: Bad_link.cgi problem In reply to
Seems to be a netscape thing.

I don't know why... maybe alex can explain it, or one of the HTML people, but if you will just
add a

print $IN->header();

to the sub main routine, anywhere at the top of it, like:

Code:
sub main {

# Define the variables
# ---------------------------------------------------
my ($id, $db_links, $rec, $confirm);

# Get the Links ID number from the input.
$id = $IN->param('ID');
$confirm = $IN->param('confirm');

print $IN->header();
The problem goes away, at least on the sites I was able to test on right now. For some reason, NN is eating the print header line, the server is seeing it, since a 500 error is not being generated, but NN is not acting on it properly.

I'm having computer problems, and will be adding a new machine tomorrow, but the past day and today, i'm limited in what I can test or do here.


PUGDOG« Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Plugins:http://LinkSQL.com/plugin
Quote Reply
Re: [pugdog] Bad_link.cgi problem In reply to
Links SQL 2.0.5 was released 8/14 and Bad_Link 2.1.0 is shown as last updated as 6/21 -- is it functional under the latest Links SQL version? (The version on www.linksql.com looks to be an even older one.) The reason I ask is because I just installed it (got the registration number problem fixed) and get the following errors with debugging turned on:

Links (16037): Links::environment called at /path/to/admin/Links.pm line 487 with no arguments.
Links (16037): Links::fatal called at /path/to/admin/Links/SiteHTML.pm line 201 with arguments (Invalid method: site_html_bad_link (bad_link.html) at /path/to/admin/Links/SiteHTML.pm line 201.
).
Links (16037): Links::SiteHTML::_compile called at /path/to/admin/Links/SiteHTML.pm line 25 with arguments (site_html_bad_link).
Links (16037): Links::SiteHTML::display called at bad_link.cgi line 59 with arguments (bad_link, HASH(0x82f8050)).
Links (16037): main::main called at bad_link.cgi line 24 with no arguments.

The only change I've made anywhere is installing the Days_Old plugin, and nothing jumps out at me as being incorrect about what I'm doing. The ID=X variable is shown as being correctly received in the 'CGI Input' section of the debugging screen.

Dan
Quote Reply
Re: [Dan Kaplan] Bad_link.cgi problem In reply to
Looks like pugdog needs to update it.


Last edited by:

PaulWilson: Sep 13, 2001, 11:11 AM
Quote Reply
Re: [Dan Kaplan] Bad_link.cgi problem In reply to
Do you have a bad_link.html file in your default templates directory?

During the 2.03...2.05 time period, there were a lot of subtle changes phased in, and modules/routines got moved around in links. Compatibility on a 'code' level is sort of version dependent.


PUGDOG´┐Ż Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.
Quote Reply
Re: [pugdog] Bad_link.cgi problem In reply to
Quote:
Do you have a bad_link.html file in your default templates directory?
Aha, good thinking. It was installed into the 'default' templates directory, but not in the custom one I was working from. I Hadn't thought of that. Seems to be working correctly now, aside from all the template tags I need to update, not that that has anything to do with the plugin itself.

I'm obviously not fully familiar with the plugin yet (or any aspect of Links SQL 2.x, for that matter), but I don't see anywhere to set an admin email address for sending notification of the bad link submission. Am I missing something, or is the thinking that people would just check in from time to time and see what has been reported?

Dan

edit: Just remembered one thing I wanted to mention. I set the table name to use when installing the plugin as Links_Bad_Link instead of the default Bad_Link. It installed correctly under that table name, but the Edit Options section for the plugin's manager shows Bad_Link still. Doesn't seem to do anything when I edit it under the incorrect table name, but it caught me by surprise at first.

Last edited by:

Dan Kaplan: Sep 13, 2001, 6:51 PM
> >