Thanks for reaching out @ebqeric. If you’re migrating your site regularly and this includes a URL change, resetting is the best option each time before migrating.
In the case of pushing a site from staging to production, there may be some options to not make any change on production each time, so you don’t have to have Site Kit active on staging (while also registering your Site Kit constants in the even of any SALT key changes). This depends on the migration feature or plugin you’re using. If you’d like to share more details on how you’re migrating from staging to production I may be able to assist further or investigate the options.
Let me know if you have any questions with the above.
As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.
@jamesosborne thanks. The migration is done using the typical WPEngine process.
https://wpengine.com/support/copy-site/
Thanks for the update @ebqeric. From reviewing the documentation you shared, it looks like there is not an option to select specific directories to maintain on the production site. I’ll see if I can check this with a WP Engine site, although this may take a few days. In the meantime I’ve reopened this support topic. What I’m trying to determine is: 1. whether the SALT keys are changed upon each migration 2: what are the specific database tables that should not be overwritten, 3. whether files on production are overwritten or simply removed if the files are part of a plugin that don’t exist on staging.
Note also that Site Kit does have a staging plugin that allows users to view data from a live site, but using another domain (in your case a staging site URL). You’ll find more on this here. This could potentially be an option for you but again I must perform some checks first.
I’ll report back to you here once I have an update. Thank you!
The Domains do change so the Site Kit staging plugin might do the trick… but I don’t see a link to the plugin on your reply.
The link to the staging plugin can be found here @ebqeric, apologies for not including this in my last response.
I also checked WP Engine and from doing so I believe it’s best for you to only install and activate Site Kit on your production site, installing each time you make a push from staging. You can use the staging plugin as suggested above, but you will need to deactivate this each time before pushing an update from staging to production.
Let me know if you have any questions with the above.
Thanks for the follow up but i think it will be easier to reset the plugin each time I migrate to production.
No problem. You don’t need to reset the plugin on staging, as the plugin will only show data based on the staging site if you don’t use the helper plugin (as per this guide). Rather you can deactivate the helper plugin before each time you migrate to production, when you have your staging site shown data from your live site. You just need to go through the Site Kit set up each time on your production site after each push.
I’ll close this support topic but do let me know if you have any questions with the above.
