Having Fun with LocalDevelopmentJulian Medina@julianlmedina
Why go Local?● Faster● No chance of breaking the live site. Ex.Recently I found out that if I upgraded acertain plugin it wouldve somehowmagically broken the footer (dont ask mehow :)). Fortunately I tested this out Locally.● And the list goes on and on
Downsides of LocalDevelopment● From personal experience, it can be a dragtaking over an existing site and working on itlocally. This has included taking over a sitewith >10 MB Database and a pretty bulkywp-content directory.● Some clients seem to not like it eitherbecause they cant see the site being built.This is often remedied by making a "Stage"site.● Different server configuration than liveserver.
Software● XAMPP● MAMP (If youre on a Mac)● WAMP● Homebrew + MySQL (Havent tried it yet)
Starting a site locally● Install WordPress locally● Develop the site● Upload the site via an FTP Client or SSH.● Upload the Database via phpMyAdminWarnings● Links may not work after going local● Site may not function because youre missingsomething.● A whole lot of other things can go wrong...
Existing live site to local tips● Good ways of troubleshooting seem toinclude deactivating all plugins. This caneither be done through phpMyAdmin orrenaming your plugins folder.● A good last resort (that ended up working),delete the entire WordPress directory locallyand re-download via FTP.
Great Sites for Help● WordPress Codex (http://codex.wordpress.org/Moving_WordPress, http://codex.wordpress.org/Installing_WordPress_Locally_on_Your_Mac_With_MAMP)● Google● Smashing Magazine - Developing WordPress LocallyWith MAMP (http://wp.smashingmagazine.com/2011/09/28/developing-wordpress-locally-with-mamp/)