This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is developing a site and trying to use pay as you go credits for automatic translation with WPML. The site involves multiple domains on the same server. WPML keeps cycling between the different domains and disabling pay as you go credits for automatic translation. The client cannot add new domains since they point to the same server and will not accept a migration code even when logging in separately on each domain.
Solution:
We recommend following the steps outlined in the documentation for managing automatic translation subscriptions for multiple sites. Specifically, you should ensure that each site is properly connected. Here are the steps:
1. Take a full site backup. 2. Use the "Move site to new URL" option in the migration wizard. 3. Unregister the WPML site key for the sites involved and register them again using the guide on using Advanced Translation Editor when you move or use a copy of your site. 4. After re-registering, connect the sites to the main domain, clear all cache types, and verify if the issue persists.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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. If problems continue, please open a new support ticket at WPML support forum for further assistance.
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.
Background of the issue:
I am developing a site and trying to use pay as you go credits for automatic translation with WPML. The site involves multiple domains on the same server.
Symptoms:
WPML keeps cycling between the different domains and disabling pay as you go credits for automatic translation. I can't add the new domains since they point to the same server and will not accept a migration code even when I log in separately on each domain.
Questions:
How can I use pay as you go credits for automatic translation with multiple domains on the same server?
Why does WPML cycle between different domains and disable pay as you go credits?
How can I add new domains that point to the same server without encountering issues with the migration code?
Somehow, you have disconnected from the chat. So I have moved the chat to a ticket.
Please note that I am unable to access: hidden link. It shows a "This site can’t be reached" message (refer to the attached image for more details).
In the Advanced Translation Editor, we are seeing multiple entries for this URL. So is it a copy of hidden link? It would be helpful if you could share the list of site URLs you have currently connected to WPML’s Advanced Translation Editor.
The development site is not a duplicate of pulpdent.com. We are refreshing the theme and structure of the site and refresh-pulpdent.pantheonsite.io is branched off into its own database and development codebase. On the development site, we are not using a .it TLD. On the refresh site we are using a folder structure (refresh-pulpdent.pantheonsite.io/it) for translated content.
Also, refresh-pulpdent.pantheonsite.io is not even actually a copy of refresh.pulpdent.com. They are the same site. Both URLs resolve to the same server.
That seemed to be the strategy that worked since the pulpdent.com domain pointed to a different IP address. I had actually started down the path you suggested prior to seeing your suggestion, but it does make sense to be able to set up a connected site via the alternate server. I was able to set it up on the main site (even though we do not wish to automatically translate on that domain at this time since the content is about to be replaced).
I would suggest the authentication for pay-as-you-go might benefit from some sort of IP address lookup to see if the domain matches the same server as one that is registered for the detected URL.
