Is there a better way to work on a child theme locally? Or should I work live? Here’s the issue.
GoDaddy or maybe all web hosting has this complicated process to go live from my MAMP Local Host. If I want to show my client daily updates I have to do this:
Edit localDB.SQL Find and replace local url with live urls
Copy local wp-config.php file and edit to match live wp-config.php or just replace local wp-config.php file with live wp-config.php file. Maybe this can be done once and reused each time or does the wp-config.php absorb other changes while I’m working on the child theme? If this is so then I have to go through a similar process with this file as with the database file.
Convoluted upload process from GoDaddy:
Importing sql files into mysql databases using phpmyadmin
Even when everything is done right not all local changes will transfer:
– I still have to go into WordPress Dashboard and reset Permalinks
– I still have to go into WordPress Twenty Eleven Theme Customizations Tab and all customizations have to be reset.
– Who knows what else doesn’t get transferred. I wonder if plug-ins have this same quirk.
Seems to me if I want to show my client my progress I should work live and get some plug-in that manages passwords so I can allow client views by just switching on and off password access. A GoDaddy supervisor recommended this. But then I watched an excellent lynda.com lesson that seems to stress a local environment for developing a child theme, “WordPress 3: Building Child Theme”s with Morten Rand-Hendriksen. His lessons are so thorough and well done that I think I can accomplish things that are normally beyond the scope of my career path or expertise. So I’m compelled to follow his lessons verbatim.
So what would this be the “Best Practices”?
- The topic ‘Best Practices for working locally or live?’ is closed to new replies.