If this workaround didn't help, I would need to look closely at your site, so I would need to request temporary access (WP-Admin and FTP)
– preferably to a test site where the problem has been replicated if possible –
in order to be of better help and check if some configurations might need to be changed.
Your answer will be private, meaning only you and I can access it.
❌ Please backup your database and website ❌
✙ I would need your permission to de-activate and re-activate the Plugins and the Theme and change configurations on the site. This is also a reason the backup is critical.
✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site.
Thank you for your response. Unfortunately it is only the production environment that has this issue, the staging or test environment works correctly. Also, WP_HOME and WP_SITEURL are not defined in the wp-config file.
My solution will begin with attempting to:
1) Reset and reconfigure the WPML plugins, perhaps even uninstalling and reinstalling them
2) Reaching out to the preferred translator for auto translation to ensure their license keys are applied to the production site rather than the staging one.
I'm not confident that deactivating plugins and the theme will provide a solution as this is a fully customized theme developed specifically with a dependence on plugins such as ACF, which will result in significant errors and issues if deactivated. So I will attempt to address WPML directly as this is the only plugin currently presenting and issue with the site.
Nothing as of yet has been translated. I'm attempting to fully uninstall and reinstall the plugins but the downloads page of WPML.org isn't allowing downloads and is delivering XML error messages for each of the plugins instead.
As far as attempting to translate a page, this is not possible as the issue is related to the automatic translations.
1- Go to Plugins-> Add New-> Commercial tab
2- Unregister WPML
3- Go to your WPML.org account
4- Delete the site's key
5- Create a new one
6- Go to your site's dashboard and register the new key
Thank you for your reply. I have also followed these steps and it did not resolve the issue. My next solution is to remove and reinstall all of the WPML plugins but I cannot download them in order to do that.
Our systems team is working on the download issue, but you can use the essential plugins (CMS, String Translation) to check if re-installing them will fix the issue.
However, I think the issue is not related to WPML plugins if they work correctly on your staging site. Are there any differences between your staging and live sites?
Thank you for working on the downloads issue. My guess is that the launch of the site and migration of the plugins from staging to production may have caused an issue such as an incomplete transfer of the files or database.
The difference between staging and the live site is the MySQL version:
I think it could be migrating that caused the issue. How about the following test?
Please use one of the following plugins to copy the staging site and install it on your live site or a local server to check if the issue is replicable.
The local, staging and production environments are in sync with the exception of certain settings which should not be disabled in the live environment like API keys for things such as Google Maps, Contact form recipients, indexing, site URL, administration users, etc. as well as new content and posts that the client has published in the live site since launch.
The only issue with the live site is related to WPML, hence the desire to reinstall WPML fully, and possibly the connection to Blend (the translator) which I am working with them to ensure it is the live and not the staging environment that they are connected to.
