For now, if you do need this fast, you could always change your options to show 99 posts (or however many you do have) and then they should all pop into view.
Urgent because I need to get rid of my current WordPress install for security reasons. Thanks for the idea though, worked like a charm.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
WordPress v1.5.1.3 plugs all know security holes, except for one that the developers are currently working on. If your server has register_globals disabled, which it should as a default security measure, then you will not be effected by the current security hole. The developers are working hard to not only plug this current security hole, but to also plug all future register_globals security holes. But, as any security expert will tell you, register_globals is one big security hole and should be disabled by default.
You best security defense is the quality of your password.
Your second best security defense is staying up to date.
As far as I know, it wasn’t register_globals anyway, it was a javascript component of the Rin theme. Whatever caused it, my site has ALREADY been hacked and I can’t really risk it happening a second time.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Rin only has two javascript components. One generates quicktag buttons in the comments form, the other causes modern browsers, like Firefox, to smoothly scroll to the #top and #bottom anchors when selected (rather than leaping to them as is the default behavior). Both javascripts have been around for quite some time. They have no known security holes, and there is no way that they could compromise your security.
If you are seriously considering the “slash and burn” security method, you might as well just take yourself completely offline. Yes, WordPress does have known and possibly unknown security holes, but so does MovableType, phpBB, the software that your host uses to manage their servers, PHP itself, your email application, your web browser, and even your entire operating system.
A word of advice, don’t “slash and burn” to avoid security holes. You’ll only make it harder on yourself, and you will eventually run into more security holes along the way. Instead, simply adapt, backup regularly, and take precautions.
There’s no slashing and burning involved, I am simply switching from a package that I know to be highly vulnerable (WordPress, given that it got me hacked) to one that is slightly less vulnerable (Movable Type)
EDIT: On the subject of staying up-to-date, I was using WordPress 1.5.1.3, the latest version, so that cannot be used as an excuse for the flaws
1.5.1.3 is NOT the latest version. 1.5.2 has been out for awhile. You may like Westi’s Version Check plugin that alerts you when WordPress is out of date:
http://blog.ftwr.co.uk/wordpress/wp-version-check/
It was when he was hacked.
