Clutters up database

Hello @mcneiljv ,

I am sorry to hear that you had issues.

> I was creating a new staging site and I had to stop the staging process in the middle of deployment because I added a wrong setting,

It would be interesting to know what “wrong” setting you used. This could be helpful for other users and of course to improve the plugin or the UX.

As you already said WP Staging works well with the default settings.

I understand your frustration but it would be nice if you keep fair and do not blame the plugin for selecting a “wrong” setting and forcing wp staging to overwrite its default settings which usually make it very reliable.

There is only one reason to change the default settings and this is if you want to get more cloning speed out of the plugins default settings.

More cloning speed means more processing power needs to be assigned. If you have a very big website with lots of traffic and a server which already runs on its resource limit, then it’s not a good idea to increase and overwrite any of the default wp staging settings.

This is why we have so many warnings and explanations besides the wp staging setting.

As a responsible web developer for a big website with lots of traffic you know that if you create multiple clones of your same website including all database tables that your server could potentially run out of resources. This can be the database, the free available storage space in the filesystem and so on.

You could easily prevent this if you checked first if there are enough resources left on the production site before you decide to create another clone on top of the other clones or if it’s worth to try to tune up the WP Staging performance settings.

> but it writes directly to your site’s database which I find pretty invasive.

Yes, the free plugin has the only option to create a staging site in the main database.
This is what it’s description also says, but you had no issue with that fact when you installed the plugin the first time, so I can not follow that argument.

Again, I feel with you but YOU are the developer of your site and it’s in your responsibility to use a plugin in a way it is intended to be used.

WP Staging will not break any website as long as you use it in a responsible way!

If you like to let me know more details about what you did exactly when your website stalled I can offer you to investigate into this issue and will probably be able to let you know how you can prevent this for the future. Beside of that, from the information I’ve got from you, it’s likely that your issue does not seem to be the fault of the plugin.

Cheers
René

• This reply was modified 5 years, 9 months ago by Rene Hermenau.

René,

As you know, before setting up a staging area you have to select which DB tables you want the plugin to create and the content. I misclicked and selected a DB table that I did not want on my staging site. I then hit the stop button to discontinue this staging deployment. This is when my site broke. I had to FTP into my plugin folder and delete the plugin for my site to actually come back. This was my issue with the plugin. I have since then found another solution to running a site for staging. Thank you for your time.

Best,
Jamie McNeil

Hi @mcneiljv

I’m interested to know the ‘other solution’ you found to running your staging sige.

Thanks,
Kristine