It looks like the issue has now been resolved — thank you very much for your help and for cleaning up the domain connections. We really appreciate your support.
To prevent this from happening again in the future, we would like to clarify one important technical detail.
We use a WordPress base installation that we clone for new projects. Before activating WPML on a freshly cloned site and registering it with a new account, what exactly should be removed from the database to ensure a completely clean WPML / ATE state?
Specifically:
- Which database tables (if any) must not be present?
- Which option records (e.g. installation ID, registration data, ATE-related entries) should be deleted before activating WPML on a cloned site?
We want to make sure that no previous site identity or alias linkage can be carried over accidentally.
Thank you again for your assistance.
Best regards.
It looks like the issue has now been resolved — thank you very much for your help and for cleaning up the domain connections. We really appreciate your support.
To prevent this from happening again in the future, we would like to clarify one important technical detail.
We use a WordPress base installation that we clone for new projects. Before activating WPML on a freshly cloned site and registering it with a new account, what exactly should be removed from the database to ensure a completely clean WPML / ATE state?
Specifically:
- Which database tables (if any) must not be present?
- Which option records (e.g. installation ID, registration data, ATE-related entries) should be deleted before activating WPML on a cloned site?
We want to make sure that no previous site identity or alias linkage can be carried over accidentally.
Thank you again for your assistance.
Best regards.
It seems you've selected "I just logged in from a secondary domain" in the WPML migration wizard on your Website earlier, and WPML thinks that the new domain is the same as the old domain, hence keeping the connection. To remove the connection, you need to edit the database and in the wp-options table, remove the wpml_tm_ate_secondary_domains data. I've done it for you and it's fixed now.
Thanks for your patience. Our 2nd Tier Support checked, and they have requested that you recheck the accounts page and let us know if you can still see other domains showing in your https://wpml.org/account/manage-credits/ section.
The topic ‘[Closed] Automatic translation issue recurring across multiple WPML accounts (related ticket linked)’ is closed to new replies.
