Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with managing WPML credits across a multisite environment on WPEngine, which includes a main site and a child site, as well as staging and development environments. The client is unsure about the correct workflow for handling WPML credits when copying from production to staging and development environments.

Solution:
1. We requested the client to provide the full addresses of the domains currently available under their wpml.org account, including the protocol and whether they include WWW.
2. After receiving the necessary information, we cleaned up all previous instances of the client's sites, including duplicates and old domains.
3. We then linked all 6 URLs together to ensure that all credits and content are linked, preventing the creation of new instances.
4. We advised the client that no specific workflow is needed when moving sites between different environments, as long as the URLs remain linked.

If this solution doesn't look relevant to your situation, please open a new support ticket.

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.

Tagged: 

This topic contains 36 replies, has 4 voices.

Last updated by Ilyes 1 year, 6 months ago.

Assisted by: Ilyes.

Author Posts
December 14, 2023 at 1:55 am #15060177

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

It turns out that we need to clean-up some instances of your sites that were created, these are duplicates and old domains that you used.

To make sure that we have the right domains, please tell me which domains you have available under your wpml.org account at the moment, and if they are the domains you are going to use from now on (Please include the full address including the protocol example : Https or http, does it have WWW or not) and then we will merge them all if possible into one at the server side and hide the domains that are NOT available, this will leave only one instance of each domain.

Looking forward to your reply,

Best,

December 14, 2023 at 4:39 pm #15066663

johnM-108

There are three environments (production, staging, development) with two sites as of this moment:
hidden link
hidden link
hidden link
hidden link
hidden link
hidden link

This is a multisite environment which will add new child sites in the future, so any solution you come up with will need to take that into consideration.

December 16, 2023 at 2:01 am #15076417

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello again,

Thank you for your patience,

Here is a video explaining how we could go from here and what needs to be done the next time you add sub-sites: hidden link

After we ensure that all 6 instances are linked under the same organization, we could start cleaning any duplicates from our servers.

You can please create wpmladmin user on all 6 of them, make them accessible and let us know once linked? I could then verify with you if they were linked correctly.

Best,

December 18, 2023 at 2:55 pm #15085379

johnM-108

Ilyes,

The wpmladmin user/pass is available on all environments. The "Server Protection Details" for the dev environment follows the same pattern. If you need more info, please create a private reply for me to share.

Let me know if you need anything else.

December 21, 2023 at 6:20 pm #15113031

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

Thank you for your patience,

We have been able to clean up all the instances that were created previously.

From now on, we highly recommend to keep all 6 URLs linked together, this setting will ensure that all credits and content are linked, no more new instances to be added and no specific workflow to follow when moving your sites to different environments.

Please let me know if you have any questions,

December 21, 2023 at 7:34 pm #15113223

johnM-108

My primary question right now regards overwriting the Staging (STG) or Development (DEV) environments within the WPEngine admin. They refer to this as copying the environment.

In the attached image, you'll see the interface, in which case I will be checking the "All database tables and file system" option to ensure the site I'm working-on is identical to the Production environment I'm copying from.

Now, when I do this, I'm fairly certain that when I first visit the WPML admin section of the newly overwritten STG/DEV environment, it will give me some message asking if this is a copy of a site or if I've moved the site. And, I'm pretty sure that the site keys will be wrong as well.

Can you give me direction on this situation, how to approach it without disconnecting anything?

WPE Copy Environment.png
December 24, 2023 at 9:47 pm #15125109

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

The Copy/Move banner is actually normal to pop up each time you overwrite or push the site,

In you case, you should always choose "copy" and if asked if you want to share credits, you then link it using the migration key like this : https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/#wpml-migration-wizard

This way, each time you get this banner, you are telling WPML that you are still working on the same "organization" where all these sites are linked.

I hope that it clear, please let me know if you have any questions,

Best,