On Nov 30, 2007 2:51 PM, Earnie Boyd earnie@users.sourceforge.net wrote:
Quoting Skip Taylor avskip@gmail.com:
On Nov 30, 2007 12:14 PM, sander-martijn lists@severeddreams.com
wrote:
Well if that sql works and in turn the database is accurate but the array is empty (an assumption i'm making from the error) then it looks like the array is likely getting lost in the php somewhere. It could take quite a bit of messing around to track down exactly where this is happening.
What I would suggest doing at this point before trying anything else if you haven't modified anything in core and have put all your modules in /sites/all/modules/ is to backup your entire site directory, download a fresh copy of drupal 5.3, replacing /sites and /files with your folders and uploading the whole thing. Since the site setup, themes, modules and uploaded files should be in those two folders that should work fine and shouldn't take more than about a half hr to hr (depending on ftp speed). If it still doesn't work then it's one of your modules or something in the database.
I'll give that a try and see what happens. As to messing around with the code, I'm not a PHP or MySQL programmer so I doubt it would do much
good.
It's more a minor inconvenience as I rarely use the setting. I was going
to
submit this as an issue but can't figure out what category to put it in.
Maybe you're just running out of memory? To .htaccess add ``php_value memory_limit 64M''. You might also add ``php_value display_errors 1'' temporarily to see if it displays an error.
That occurred to me. If it were just running out of memory, when I disabled the modules wouldn't that have freed the memory up? I'll try to completely remove a couple of modules and see if that does anything anyway.
Thanks, Skip