How to keep your WP database squeaky clean

8 Tips for Keeping a Squeaky Clean WordPress Database  Useful post by Sarah Gooding at http://wpmu.org/

“Optimizing your database is a necessary part of WordPress housekeeping. Things can start to pile up in there… post revisions, old spam comments, etc., and your blog can start to get sluggish. We’ve gathered a number of solid tips for getting your database into shape without having to be an expert”.

Need to look at the WP-Optimize plugin mentionned.

More problems with this site (and postscript)

Just lately yet again I found that this blog  fails to load reliably. When it does it won’t always let me log in and on refeshing fails to load again. In addition the other installations here don’t load reliably -   http://terrywassall.org/elgg and http://terrywassall.org/wiki/.  Worst of all is http://terrywassall.org/blogs/ which either won’t load at all or, if it does, has no formatting as if it can’t find the css or theme files. Once again 34SP.com came to my rescue. Apparently one of my scripts has been trying to increase its memory allowance. This has been allowed and all seems to be OK again.

I have been trying to think of anything I might have done to mess this installation up and the only thing I can think of is that, perhaps coincidentally, various troubles date back to when I disabled and deleted the BuddyPress plugin and themes and upgraded WPMU to 2.9.1. The whole site has been flaky but the http://terrywassall.org/blogs/  has been the least reliable bit of it. I think I may completely remove the MUWP install in the blogs folder and start from scratch with a new install of 2.9.2. I’ll see how it goes. As I say, all seems to be OK for the moment.

Postscript: Just got a message from 34SP re: the problem. It seems there are a number of security modules on the server and one of these picked up on a script trying to change the allowed memory. Apparently this is something  a lot of bogus scripts do. When this happens, to protect the server, it blocks user access. Although this may seem a little harsh, as 34sp admit, the security module is just doing its job. I don’t think we can argue with that. It would be nice, however, if there was a process where the  site owner/admin was contacted about the problem rather than waiting for them to notice themselves. I sometimes don’t visit this site for up to 2 weeks and I have no idea how long it has been down for. I assume the offending script (is that the same as a php file?) could be identified as well. If is is a rogue script this would be useful information I would have thought!

Copyright © terrywassall.org
work in progress

Built on Notes Blog Core
Powered by WordPress