In case of any serious trouble, reverting the changes can be tough, and especially if your database data has been corrupted as well.This means dealing with FTP or other mechanisms, which takes time. In most cases, you’re going to need to copy new site files manually onto the server. If it’s rented hosting that you’re dealing with (like from any web hosting company such as Bluehost or SiteGround) then causing more serious server errors – which can happen during development – can lead to an eventual ban from the platform. Developing on a live site = developing in a live hosting environment.In some cases, the sole fact of a visitor trying to navigate to a site mid-development can break things and cause uncommon site or server errors. The obvious consequence of working on a live site is that whatever you do is immediately visible to your visitors.And especially if that work involves anything development-related. Hence, the need to install WordPress locally.īasically, working on a live site and on a live domain (available publicly) isn’t the best of ideas. Building WordPress sites can sure be fun, but only if you get to do so in a stress-free environment that allows you to experiment freely.
