[Resolved] Split: How to update the recruiter on the transalted page?
This thread is resolved. Here is a description of the problem and solution.
Problem: The client encountered issues while updating recruiter information on translated destination pages using Elementor. Specifically, they were unable to save changes and received a warning about potential loss of edits when trying to replace a recruiter on the Finnish version of a page. Solution: We recommend ensuring that WPML and Elementor are used in accordance with our compatibility guidelines, which can be found here: https://wpml.org/documentation/plugins-compatibility/elementor/. The issue described was not directly related to WPML. When editing translated pages, it is crucial not to use Elementor directly but to utilize WPML's Translation Editor. This approach was successfully used on the German version of the page, where the recruiter was correctly updated. To resolve the issue on the Finnish page, the client should update the information using the Translation Editor to ensure the changes are properly saved and displayed.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please do not hesitate to 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.
Yes, it works. We also added new people. What was the reason this issue showed up? Was it due to an update? How did the code get corrupted?
THANK YOUUUUUU!
-----------------
We’ve encountered a new issue while updating recruiter information on our destination pages. Specifically, we were manually updating the assigned recruiters—like changing to Hazal on the Croatia page:
🔗 hidden link
After this, we attempted to update the translated pages as well, and on some we manged, but tt the beginning of May, someone made changes to the website (we're not sure who), and the site eventually crashed. We managed to recover it, but since then, we've encountered issues when trying to edit translated destination pages.
🔗 hidden link
On this page, we’re trying to replace Karlo with the correct recruiter, but we can’t access or save any changes. we received the following warning when attempting to edit using Elementor:
"Warning: Edits you're about to make will be lost. You are about to edit this translation using Elementor. Any changes you make will be lost the next time you send this page for translation."
We also received a suggestion that we need to edit the page in a specific way to allow changes, but we haven’t seen any clear option for that. At the moment, we are unable to change the recruiter from Karlo to the correct person.
Could you please help us resolve this and explain the proper process for editing translated pages without triggering this warning or losing our updates?
The problem you mentioned, which occurred at the beginning of May, is not due to WPML, as far as I can understand. When I edit the Croatia page in English, the default language, I see an error message: 'Updating failed. The response is not a valid JSON response'. However, from the front end, I can edit with Elementor, and I can see that the recruiter has been added with an Image Box element. Please see the attached screenshot. You should not edit the translations with Elementor to replace the recruiter. You should edit it with WPML's Translation Editor, and this is how it is set for this page. As proof of this, I can see that it worked in the German language (the pencil icon shows and Hazel is the recruiter on the German translated page. I can see that the Finnish language needs an update (as indicated by the circled arrow icon). Please see the attached screenshot. It appears that you need to update Finnish with the Translation Editor to ensure Hazel is displayed as the recruiter in Finnish.
Just to clarify — we never edited the translated pages in Elementor. We only changed the recruiter images (using the Image Box) on the default English page via Elementor. We didn’t make any changes to the translated versions in Elementor.
Since it’s only image updates we made, do we need to update the media library or take any specific steps so we can edit the page again without getting the JSON error?
I see on the link you sent: “WPML lets you use the Elementor editor to create your designs in each language, so there’s no limit to how unique or complex your pages can be.”
Changing images would be like changing a design, not the text, on the different translated versions.
OK, good that you are not editing the translated page with Elementor if you don't want a different design for the translated page.
You asked: "Since it’s only image updates we made, do we need to update the media library or take any specific steps so we can edit the page again without getting the JSON error?"
You don't need to update the media library or take any other specific steps except updating the translation with WPML's Advanced Translation Editor. This will update the image, name, and link of the recruiter. I tested it with the Dutch translation, and it worked. I opened the translation with the Advanced Translation Editor and noticed a few strings that needed updating. I noticed that the media for Hazel also required an update. Please see the attached screenshot, hazel-in-ate.jpg. Then I saw the Dutch page has been updated with Hazel's image. Please see the before-and-after screenshots. before-update.jpg and after-the-update.jpg.
As for the JSON error, I don't see how it is related to WPML.
To summarize, you need to update the translations using the Advanced Translation Editor to reflect the changes.
Yes, this is correct. You must adhere to one method of translation and refrain from mixing between them. In your case, you should stick to translating the content with the Advanced Translation Editor.