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

Considering a local development server


Maybe you have a PC or Mac-based development server? Here's why you should:

  • Develop themes more easily before uploading to the live production server

  • Test compatibility of WordPress and plugin upgrades plus new code

  • Ultimately, because it's better to screw up a beta site than a live site!

So what sort of local setup is best? There are examples aplenty, XAMPP from Apache Friends being the most easily installed, user-friendly, cross-platform candidate:

That's a fair bet for most of us with its Apache, MySQL, and PHP configurations largely matching those we can, to a greater or lesser extent, tweak on the live box itself. But what about unmanaged hosting users, who would ideally mimic the remote box locally, as well as for all of us wanting to max out on best security practices for site development? In these cases, setting up just any old local server isn't a bad idea, it just isn't the best idea.

Using a virtual machine

In...