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

[UPDATED] Bad-Link reporting Plug-in

Quote Reply
[UPDATED] Bad-Link reporting Plug-in
Minor mods and fixes. Should work fine out of the box.

PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
I am getting a page not found error when attempting to report the link bad.

I double checked that the Bad_Link.cgi is chmod 755. That was ok. I made sure that I cut and past the call line directly into the link template.

Am I overlooking something?


Dan Oakeson
http://www.AssociateCash.com
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Bad_Link.cgi is actually Lower case. so when you link to it, you should link to bad_link.cgi and it should be there. is the newly updated version released cause it still isn't working. i am going to start investigating this plugin stuff.

Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
same problem here
It does not work with lower or upper case. tried everything i know of it gives you an 404 error message or 500 error message.

Have tried the previous three fixes and still not working

I am Giving up on it........!

Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
In Reply To:
A fatal error has occured:

Undefined subroutine &Links::Plugins::get_plugin_user_cfg called at bad_link.cgi line 57.

Please enable debugging in setup for more details.
I feel dumb that I did not check for upper or lower case. Thank You. But know I get this error above. Anything else that I may have goofed up.

Dan Oakeson
http://www.AssociateCash.com
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Can you point me to it on your site?

I install this on 2 or 3 sites before I release it, so it has to be something quirky that is on some systems not others.

Also, there is a problem with the "default" values in the columns, I haven't heard from Alex on that, but I can't set the default Int value to '0'.

PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Hi Pugdog:

Getting the same errors as others .... Server 500 errors. Checked the file manually, all looks okay, path to perl is right, paths to the 'admin' directory are okay .... Am running the latest version (installed it today).

Regards,


Clint.

--------------------------
http://www.AffiliatesDirectory.com - Affiliate Programs Directory
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Hi Pugdog,

First I just want you to know that I really appreciate your effort both in making the plugin and in the support you are providing.

You can view what I have here
http://www.associatecash.com

If you need anything else just let me know.

Dan Oakeson
http://www.AssociateCash.com
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Can you tell me what the error log says when you get that 500 error?

Alex sent me a file that would hopefully fix the column bugs, but it didn't. I have a feeling the same problem is plaguing all my scripts/plug-ins since they are all pretty much the same, and seem to be generating the same error on other people's sytems.

The first few are always a learning experience, and once this elusive bug is nailed, everyone will be able to avoid it in the future.

PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Pugdog:

Just one quick thought (I know I'm tempting fate) .. In the options setup for Badlink I note the default table that it points to is Bad_Link.

If you have an upgraded database and use a prefix such as _ so the actual table name is _Bad_Link, could that cause a problem .... only stabbing in the dark here!


Regards,


Clint.

--------------------------
http://www.AffiliatesDirectory.com - Affiliate Programs Directory
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Here you go. Sorry it took so long to get back at you.

In Reply To:
A fatal error has occured:

Undefined subroutine &Links::Plugins::get_plugin_user_cfg called at bad_link.cgi line 57.

Please enable debugging in setup for more details.

Stack Trace
======================================
Links (4685): Links::environment called at /big/dom/xassociatecash/cgi-bin/Beta/admin/Links.pm line 452 with no arguments.Links (4685): Links::fatal called at /big/dom/xassociatecash/cgi-bin/Beta/admin/GT/Base.pm line 212 with arguments (Undefined subroutine &Links::Plugins::get_plugin_user_cfg called at bad_link.cgi line 57.
).Links (4685): GT::Base::__ANON__ called at bad_link.cgi line 57 with arguments (Undefined subroutine &Links::Plugins::get_plugin_user_cfg called at bad_link.cgi line 57.
).Links (4685): main::main called at bad_link.cgi line 20 with no arguments.

System Information
======================================
Perl Version: 5.00503
Links SQL Version: 2.0.1
DBI.pm Version: 1.13
@INC =
/big/dom/xassociatecash/cgi-bin/Beta/admin
/usr/local/lib/perl5/5.00503/i686-linux
/usr/local/lib/perl5/5.00503
/usr/local/lib/perl5/site_perl/5.005/i686-linux
/usr/local/lib/perl5/site_perl/5.005
.

CGI INPUT
======================================
ID => 577


CGI Cookies
======================================
password => RLULYVPNXR


ENVIRONMENT
======================================
DOCUMENT_ROOT => /big/dom/xassociatecash/www
GATEWAY_INTERFACE => CGI/1.1
HTTP_ACCEPT => image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, */*
HTTP_ACCEPT_ENCODING => gzip, deflate
HTTP_ACCEPT_LANGUAGE => en-us
HTTP_CONNECTION => Keep-Alive
HTTP_COOKIE => password=RLULYVPNXR
HTTP_HOST => associatecash.com
HTTP_REFERER => http://associatecash.com/Shopping/Music_Movies/index.shtml
HTTP_USER_AGENT => Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)
PATH => /bin:/usr/bin:/usr/local/bin
QUERY_STRING => ID=577
REMOTE_ADDR => 12.111.167.139
REMOTE_PORT => 1028
REQUEST_METHOD => GET
REQUEST_URI => /cgi-bin/Beta/bad_link.cgi?ID=577
SCRIPT_FILENAME => /big/dom/xassociatecash/cgi-bin/Beta/bad_link.cgi
SCRIPT_NAME => /cgi-bin/Beta/bad_link.cgi
SCRIPT_URI => http://associatecash.com/cgi-bin/Beta/bad_link.cgi
SCRIPT_URL => /cgi-bin/Beta/bad_link.cgi
SERVER_ADMIN => webmaster@associatecash.com
SERVER_NAME => associatecash.com
SERVER_PORT => 80
SERVER_PROTOCOL => HTTP/1.1
SERVER_SOFTWARE => Apache/1.3.17 (Unix) mod_macro/1.1.1 PHP/4.0.4pl1
UNIQUE_ID => Oqbhbz9f3WcAAB6VRBw
Thanks!


Dan Oakeson
http://www.AssociateCash.com
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
It shouldn't make a problem. All the calls to the database go through the SQL module, and that should prefix tables properly. It's worked on all my databases so far.

The problem is something more insidious, and I'm not sure why it works for some people, but not others.



PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Ok. I think the problem has to do with Links::Plugins vs GT::Plugins

I'll look at the files again and make sure the right ones are loading. The thing I don't understand is why it works for some people, but not others -- and SpeedyCGI isn't the answer.



PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: [UPDATED] Bad-Link reporting Plug-in In reply to
Hi,

I'm sorry! The version that was uploaded to the download area for some reason was not the right version. The headers were wrong. I've fixed it now (again), and it should be right.

I'll make sure the other versions of the archive files are the correct ones.

I was working on a different machine (got some personal stuff going on) and it looks like all the copies didn't get updated correctly.



PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum