[Resolved] Split: Translated Custom Fields Returning Different Data
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.
You won't have any downtime. Here we're talking about re-registering your sites with WPML.org. All previous published translations are saved in your database so you're not losing translations neither.
Nicolas -- I know you say nothing will happen, but the multisite + WPML set-up on WPEngine has been very touchy, so I'm working on getting a hold on content maintenance on the site, then I will perform a backup of the site. Once this is done, I'll post the production login credentials for you and your team. Thanks.
Nicolas -- Any word on the status of this issue? I put a hold on client content updates starting last Friday through today. I'll need to let them know what's going on. Thanks.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
Please watch this video: hidden link
Try to see if you can connect the websites or if you have all the plugins network activated, then try to either install a new dummy one that won't be network activated and see if that lets you see the "plugin" menu because even on multisite installations
Ilyes -- Thanks. I see now that the WPML > Translation Management > Tools tabs in the admins of all four sites are now connected. They all indicate that I have 48342 "Prepaid credits left".
I have a few remaining questions:
1) In my wpml.org admin account dashboard, the "Sites Using Prepaid Credits" section has these four sites in the list, but a) "Credits available" is 9046 (not 48342) and b) only one site has 500 credits assigned to it. Can you explain the "Sites Using Prepaid Credits" section of the admin and how it relates to the "Prepaid credits left" number in the site admins?
2) An important thing for me to understand is how to copy environments correctly. In case you haven't read through this entire case (I don't expect you to), my site is hosted on WPEngine which provides me with a Production, Staging and Development environment.
In the future, I'm going to add the Development environment to these lists and will routinely have to copy the Production environment down to the other two in order to keep them in sync.
What is the recommended way of doing this? Am I correct in assuming that I will copy the Production environment down to one of the other two and then I just need to make sure the site key is changed back on the newly overwritten sites?
Ilyes -- Also, at this point, I don't know if I want my Staging and Development environments to have all of the credits shared with them. The last thing I want is to spend those credits in a development environment and essentially lose them.
In a previous comment in this thread, I thought the recommendation was to 1) assign prepaid credits to the Main site in a multisite environment and then 2) connect only the Child sites of that multisite environment to the Main site.
So in my scenario, I would assign most of the prepaid credits to hidden link and then connect it to hidden link
And then I would assign a small number of credits to hidden link for bug fixing and testing, and only connect it to hidden link.
Does this make sense? This is why I'm confused about the "Sites Using Prepaid Credits" table in my account only have 500 credits assigned to the child staging site at hidden link.
Ilyes -- I went ahead with my plan of copying Production down to Development. It didn't work as expected in that I couldn't just apply credits to the Development main site and connect the child site to it. I'm beyond frustrated with this whole thing, so I just connected the Development sites to the Production Main site and will hope my client or another dev doesn't accidentally choose to automatically translate the entire Staging or Development site.
I would still appreciate an answer to Question #1 in Reply# 15017999 above. I don't understand the whole prepaid credits discrepancy between the WPML admin and my site admins.
Languages: English (English )French (Français )Arabic (العربية )
Timezone: Pacific/Easter (GMT-06:00)
Hello,
I will start with explaining how the WPML.ORG profile prepaid credits section works.
There are two level of credits here : hidden link
1- First layer is how many credits does your whole profile have, which you can assign to your registered sites, e.g; you buy 60K credits, they will stay under your profile, and they can't be used until you assign some to the desired site
2- Second layer is where to assign credits and how many credits have you already assigned to each website
So if we take your screenshot as a reference, you only have 9046 credits + 500 credits already assigned to hidden link
This is where we see a problem, the second layer should always match what you see under your WordPress admin
That's why you should see 48442 Credits here too: hidden link
-----
As my colleague Nicolas mentioned before, there were more than a dozen instances of all your sites on our server side, which is mostly why the synchronization for lost at some point when migrating/copying your site.
We had similar cases before, but each one is unique by itself and there is a possibility to simply reset everything by registering all sites from scratch and re-assign credits manually, but we do not want to risk that you will encounter this problem again.
With that said, I highly suggest we give a little more time to our systems team to figure out the best workflow you can follow and test this further.
I really understand how frustrating it can be, especially with all the different versions and numbers on each site, and your patience is really appreciated,
---
In the meantime, you could temporarily disable automatic translation on the Staging / Dev sites from WPML > Settings > Translation Engines > Turn off
Or simply change the translation editor to the "classic" mode, which doesn't have the automatic translation option : hidden link
I will let you know once I get an update from our team,
Ilyes -- Thanks for the feedback. I'll have the rest of my team work on other projects until this is resolved and handle anything here myself. I'll wait to hear back from your team on this situation and look forward to learning the proper workflow for my environment.
