Based on the error it looks like they may have updated mysql to 5.0.51 which has a known bug. Check what version of MySQL they upped to.
Hmm... while I had been told they were upgrading to MySQL 5, running phpinfo() shows my they’re using version 4.1.12 which meets the ModX minimum at least. However, the problem is still there. It seems to be getting caught in a loop. I’ve set the memory limits in a php.ini in the root directory to 24M, 32M and 64M. I have it echoing the memory limit and it shows that it’s working in the phpinfo file. However, each time the exact same amount of memory is shown as being needed by the error.
Any other ideas? I’m stuck here.
Thanks!
Lonnie
Is there anything suspicions in the System Events log?
Try running the query directly in phpMyAdmin and see if it gives a better error. I tried it on my server and it worked fine (editing it to reflect my database).
I can’t find anything wrong. Here go some guesses (brain farts):
Maybe the host upgraded their host while you were working and then downgrded again causing this error. Or their upgrade was flawed.
Do you have multiple MaxiGallery calls on the same page? Are your Galleries huge..100s of pictures?
Turn off the Search Highlight plug-in, this may have a bug (I just helped another user where this was causing a problem).
Also clear out the cache since the cache could be corrupted.