WordPress Active and Development server best practices

I currently have a separate WordPress install on a subfolder /dev and the live site in the root directory. I developed the site on the dev folder and then copied it over when it was complete. I want to maintain the dev site for future enhancement testing.

Is there a better or easier way to do this using built in WordPress features like multisite?
Can anyone verify that this is a good way to approach it?

1 Answer
1

I guess your folders are linked to different domains or subdomains. I usually use a domain and a subdomain (www.domain.com and dev.domain.com, for example) to let me work in the pre-production site (not indexed by search engines, this is quite important to avoid duplicated contents and SEO problems) before applying changes to the final one.

WordPress MU is useful if you have a blog network because it lets you update themes, plugins and WP version easily (amongst other things), but I’d not say it’s useful for the purpose you’re looking for.

I’d use two different folders (mysite and dev-mysite, for example) and not use root as the production folder, because that can lead to confusion. But pointing domain and subdomain to these folders will let you work on any of them easily and update the final (production) one when the changes are ready.

Leave a Comment