Allow me to clarify that during the process of copying the entire staging instance to the live instance, we consistently encounter the need to update certain settings.
This includes indicating whether it is the original or copied site through a checkbox. Additionally, we must update the site key obtained from the WPML plugin since the site key for the staging instance differs from that of the live instance.
Managing these settings each time poses significant challenges for the client. Is there a method by which we can copy the staging instance to the live instance with minimal adjustments required?
Thank you for the answer. My primary concern isn't solely about the site key. What worries me is the additional steps we consistently need to take each time we synchronize the staging environment with the production environment (as depicted in the attached screenshot).
Even after defining the site key in the wp-config file, I still have to perform the same steps.
Please tell me how we can avoid these steps for smooth deployment.
I asked and at the moment there's no way to avoid being asked if the site has been copied or moved, so I cannot help you with that.
I don't understand the second set of screenshots. If you unregister WPML from the site, it's a given you should re-enter the license.
WPML license is related to the domain, but it's only needed for plugin updates and for using the translation editor. If you performs all updates and translations on the dev sites, you can ignore the license on the prod site.
The website is hosted on WP Engine, and we utilize WP Engine's Restore functionality to synchronize instances. This process syncs the entire staging instance to the production instance, encompassing the database, code, and all configurations.
But if you push all the files (which is a bit strange actually) from staging to prod this might still be not useful. You may ask WP Engine if there is a way to not overwrite wp-config.
