The error message:
WordPress database error: [Out of memory; restart server and try again (needed 65528 bytes)]
Just getting that out of the way :)
I just reformatted my hard drive yesterday. Spent all day (yesterday and today) backing stuff up and formatting, loading everything - ugh. I saved my XAMPP installation files, my localhost WP databases and files. Everything's up and running nicely, but I started working on a site and when I did a search on the test server, I got that error above. Happens *only* when I use the "search".
Now, I'm sure it's a setting somewhere (or, pretty sure, anyway), and it's only a localhost issue, and it *must* have something to do with the fact that I just formatted my hard drive (because I didn't have this problem *before* I wiped the slate clean) - would anyone know what it might be? At first I thought it was my PHP reaching some kind of memory limit, but it's set at 16M, and I tried to increase the limit to 20, and it had no effect (yes, I restarted Apache and MySQL).
Another *possible* problem (although I'm not too convinced of this, because - as I said before - I didn't have this issue before I wiped the hard drive) is that I've written a custom plugin that re-creates the "list pages" function in WP. It connects to the database and looks for Pages that have a certain custom field entry, then outputs those pages in order by ID. (But I also needed *one* category inserted in the middle of the list of pages, to I put in a conditional to add that in, as well.) So it's a tricky piece of code, but I've read here that custom plugins such as this might cause some issues. (This sidebar is used sitewide.)
As an aside - does anyone think that this is something the devs might be interested in seeing? Maybe for an upcoming release? I dunno - just thought I'd ask.
Anyway, I read another post on the forum here that such a plugin might leave some "open ends" and too many database queries, and it's possible that it could be causing the error. But I'm not totally convinced of it - so if anyone would like to see that code, I can provide a link to the text file, if you really think that's a possibility.
Anyway - anyone have any ideas of what I could do? I don't really care so much for *my* server, but when it goes live, I want to know that this error won't happen.