Over the course of the past few posts I’ve shown you how to clean up the post revisions in your WordPress database and limit them in the future, and how to remove the spam comments from the database as well.
Now just removing them may make things a little quicker, but to optimise things even more we need to compress the database so that the areas where those things were stored are not just marked as “deleted”, but remove completely. This compresses the database and makes it smaller. In some cases, that compression can be considerable.
To do this, we’re going to re-visit a plug-in that I’ve talked about before: Continue reading
I’ve talked before about how important it is to reduce the size of the WordPress database to make it more efficient, and showed two plug-ins recently to reduce the number of revisions stored for each post in the database.
But there is another area that can grow in the database if you’re not careful, and that’s the spam comments.
Whichever system you use to block spam comments (e.g. Akismet), they still stay in the database in case they were a false positive and you want to recover them, at least for a while.
Luckily there’s a simple button in WordPress to remove those comments, once you’re happy that they don’t need them. Continue reading
I’ve talked before about how the “ping” system works in WordPress. But there is a bit more to the ping element than just notifying other systems when a post is published.
The trouble is that WordPress apparently sends the ping when a post is published or updated, regardless of the actually time the post is set to appear.
If you only publish your posts in real time and never go back to edit them, then that probably doesn’t worry you.
But if you write a number of posts in succession and then set them to appear over a number of weeks, or if you find yourself going back and editing posts on a regular basis, then you should consider what it looks like to the ping recipients if they get a lot of pings in a small space of time, but then none for the next few weeks.
It could make your site look like a spam blog, even though it isn’t.
The solution Continue reading