This thread is resolved. Here is a description of the problem and solution.
Problem:
The client has transferred their website to a new host and needs assistance ensuring WPML functions correctly on the new site. They previously marked the site as a temporary copy and now wish to set it as the standard production site.
Solution:
We recommend following the steps outlined in the documentation to move your website to production. Specifically, you can find detailed instructions under the section 'What if the notice still appears after moving to production?' at https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
This topic is split from https://wpml.org/forums/topic/wpml-is-causing-no-storeno-cachemust-revalidate-errors-in-my-header/
This topic contains 1 reply, has 2 voices.
Last updated by 1 month, 2 weeks ago.
Assisted by: Lucas Vidal de Andrade.