Book Image

WordPress 3 Ultimate Security

Book Image

WordPress 3 Ultimate Security

Overview of this book

Most likely – today – some hacker tried to crack your WordPress site, its data and content – maybe once but, with automated tools, very likely dozens or hundreds of times. There's no silver bullet but if you want to cut the odds of a successful attack from practically inevitable to practically zero, read this book. WordPress 3 Ultimate Security shows you how to hack your site before someone else does. You'll uncover its weaknesses before sealing them off, securing your content and your day-to-day local-to-remote editorial process. This is more than some "10 Tips ..." guide. It's ultimate protection – because that's what you need. Survey your network, using the insight from this book to scan for and seal the holes before galvanizing the network with a rack of cool tools. Solid! The WordPress platform is only as safe as the weakest network link, administrator discipline, and your security knowledge. We'll cover the bases, underpinning your working process from any location, containing content, locking down the platform, your web files, the database, and the server. With that done, your ongoing security is infinitely more manageable. Covering deep-set security yet enjoyable to read, WordPress 3 Ultimate Security will multiply your understanding and fortify your site.
Table of Contents (23 chapters)
WordPress 3 Ultimate Security
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Updating shrewdly


What's worse: not upgrading and getting hacked or upgrading too early and hacking yourself? The answer is the former but, then again, it's better not to get hacked at all.

Updating WordPress isn't always a straightforward process, as many early jumpers from 2.9 to 3.0 would attest. We've been here before as well, white screens galore. Ideally Automattic would have parallel upgrade programs, one for vulnerability patching and another for candy. But they don't. Here's a typical scenario.

Jonny upgrades because he read he should. But, oh dear, there's some incompatibility with some plugin and something breaks. Great! Having whittled down to the something can't Jonny just disable the plugin? Well, no, not if it's the one paying the rent. He's thinking this through, thirteen to the dozen. How does he rollback again? Meanwhile, the traffic's dropped off the map. No pressure! You get the picture.

Think, research, update

While upgrading as soon as you can is in general good advice...