Hello,

I've encountered a strange problem with my Links Sql2. Everything was working fine and then on day I went to rebuild some changes and I got this error

Can't call method "fetchrow_hashref" on an undefined value at Links::Build::build_home line 13.

I tried changing everything back, it was just a few changes to sorting orders and such. But no luck. I set the program to Debug level 2 and it just times out, but here's the stack trace of debug level 1

Stack Trace
======================================
Links (4786): Links::environment called at /var/www/cgi-bin/links_sql2/admin/Links.pm line 431 with no arguments.
Links (4786): Links::fatal called at Links::Build::build_home line 13 with arguments
(Can't call method "fetchrow_hashref" on an undefined value at Links::Build::build_home line 13.
).
Links (4786): Links::Build::build_home called at /var/www/cgi-bin/links_sql2/admin/GT/Plugins.pm line 108 with arguments
(HASH(0x82530d4)).
Links (4786): GT::Plugins::dispatch called at /var/www/cgi-bin/links_sql2/admin/Links/Build.pm line 30 with arguments
(GT::Plugins, /var/www/cgi-bin/links_sql2/admin/Plugins, build_home, *Links::Build::build_home, HASH(0x82530d4)).
Links (4786): Links::Build::build called at /var/www/cgi-bin/links_sql2/admin/Links/User/Page.pm line 77 with arguments
(home, HASH(0x82530d4)).
Links (4786): Links::User::Page::generate_home_page called at /var/www/cgi-bin/links_sql2/admin/Links/User/Page.pm line 53 with no arguments.
Links (4786): Links::User::Page::handle called at /var/www/cgi-bin/links_sql2/admin/GT/Plugins.pm line 108 with no arguments.
Links (4786): GT::Plugins::dispatch called at /var/www/cgi-bin/links_sql2/page.cgi line 25 with arguments
(GT::Plugins, /var/www/cgi-bin/links_sql2/admin/Plugins, handle_page, CODE(0x806a44c)).

I stepped through the code but can't figure out why it would crash. I read through some other articles on changing the globals.txt but they haven't been changed and don't look anything like what the posts on this board were saying to do. Any thoughts would be REALLY appreciated, thank you so much.

Daniel

Do you get any more detailed error messages if you set 'debug' to 2? (normally a SQL section, which lets you know which command failed).

Cheers

Andy (mod)
andy@ultranerds.co.uk

---

Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!

I tried setting it to Debug level 2 but it times out and gives me a 404. I can't tell why either... level 1 is all I've got to work with unfortunately...

Daniel

Ok, leave it on level one then, and then once you have run page.cgi, check your error logs (normall /logs/error_log , but varies on servers). Hopefully that will give a bit more info on what is going wrong :)

Cheers

Andy (mod)
andy@ultranerds.co.uk

---

Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!

The debug section should also list a:

$GT::SQL::error = ....

line which ought to help diagnose the problem.

---

Jason Rhinelander
Gossamer Threads
jason@gossamer-threads.com

Jagerman> Perfect, I didn't see this part of the debug, there was a typo in the 'ORDER BY Col_Name'. Thank you so much for your help. Cheers.

Daniel