[Resolved] Automatic adjustments on translated pages
This thread is resolved. Here is a description of the problem and solution.
Problem: The client needed to ensure that changes to the original page are automatically transferred to the translated pages and wanted to be notified in WPML when translated pages need to be reviewed for translation.
Solution: We advised the client to use only one method for editing content: either the WPML Translation Editor or the WordPress editor, but not both simultaneously, as this can lead to issues. Specifically, if using the WordPress editor, it's important to switch to this option by clicking "WordPress Editor" in the language column, which disables the WPML Translation Editor.
For the Advanced Custom Fields (ACF) settings, the client should set the fields either to 'Copy' or 'Translate' depending on the desired behavior. This adjustment is crucial for ensuring that layout fields are copied and text fields are translated as intended. This can be done under ACF > Field Groups by selecting "ACF tabs blocks" and setting the translation options for each field.
Additionally, we noted that custom CSS might not work across languages and recommended adding the CSS in Appearance > Customizer > Custom CSS to ensure it is recognized in all languages.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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 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.
So, I noticed one thing in the videos you sent (thank you, by the way). In the video, you are using the WPML Translation Editor to edit the content and, at the same time, you are using the WordPress editor to input content on the translation page. That's not recommended and can lead to many issues, like the one you're facing. Please only use one method. The issue was happening because of that.
Let me explain: WPML offers you the ability to translate only the content of the page, while all the rest stays as they are (css, page options, etc). To do that, use only WPML's translation editor and never edit the page directly using WordPress.
If you want to edit the page using the WordPress editor, in a way that you can also edit the layout and other options, first switch to this option, by clicking "WordPress Editor", in the language column. See image attached. This way, WPML's Translation Editor will be disabled and you can create the translation as you wish.
_______
I was able to fix the issue in the copy I created. Please make a full website backup and follow these steps:
1. Remove the password protection from the original product and set its status to published;
2. Delete the translation of the product. To do that, go to Walltopia Products, switch the language in the top-bar (clicking on the flag), send the translation to the trash can and remove it from the trash can.
3. Switch the language back to the original.
4. Add a translation, by clicking on the "+" sign for the language, inside the original product editing page;
5. Complete the translation;
After that, never edit the translation directly, as it will cause conflicts. I recorded a video showing the steps: hidden link
Important notice: please note that there's custom CSS that is not working across languages. I couldn't find how the custom CSS that removes the shadows was implemented. To fix that, you can add this CSS in Appearance > Customizer > Custom CSS, so it gets recognized in all languages. Please check the implementation to see if the CSS selector matches what you need.
I hope this answers both of your questions, sent on both videos.
So in the video I edited the layout/blocks, but as you can see in the video, after I changed the layout (duplicated from one page to another) the new layout didn’t appear for translation in the translation module, so I had to manually translate it in the WP editor, there was no other choice.
The point of the whole thing that I want to happen is that when I make a change in the original language, that change get transferred automatically into the translated languages and all I have to do then is to click “update translation”. Unfortunately, as seen in the video, when I make a change, it is not reflected in the other languages.
Also, I don’t want to delete my translations as I’ve already went through a lot of trouble fixing issues and translated texts so this would bring me back to square one. This would also cost me credits that I’ve already used one, so it is far from beneficial for me to redo all translations as I have 10 languages and about 15 pages.
Something else to ask – the WordPress editor note states “Use only when you want to translate content from one of the few plugins that are not compatible with WPML’s translation editor or if you would like to create different designs for the same page in different languages”. I don’t think that either of those is what I’m doing. I mean I’m not doing different design for different languages.
You’re saying “After that, never edit the translation directly, as it will cause conflicts”, but what do I do when the content doesn’t even appear for translation “like it did in the video”?
I recorded one more video showing how the process must be done from scratch, showing that it indeed works on your website: hidden link
For the content not being copied, I double-checked the settings of the ACF “ACF tabs blocks” and there were some fields that must be changed. Please set your fields either to Copy or Translate, depending on what you want. Usually, layout fields are set to “Copy” and text fields are set to “Translate”.
I recorded how changes are being reflected on translations, after correctly setting the ACF fields: hidden link
As for the translations that must be deleted, it will be only once for that specific post, that was created in a way that caused the conflicts. We must delete them so we can recreate them from scratch. That's what I showed in the previous video.
Besides that, your translations that were already added are saved in Translation Memory, so you won't get charged twice. You only get charged for texts that were never translated before.
The solution:
Please set up the fields as they should, and recreate the translations. After doing that, the translations are going to work as intended.
P.S: In the video, you "changed the layout (duplicated from one page to another)". That's exactly what can't be done, when using WPML's translation editor. That causes conflicts.
"For the content not being copied, I double-checked the settings of the ACF “ACF tabs blocks” and there were some fields that must be changed. Please set your fields either to Copy or Translate, depending on what you want. Usually, layout fields are set to “Copy” and text fields are set to “Translate”."
1. Please go to ACF > Field Groups and select "ACF tabs blocks";
2. Since it has the "Expert" translation mode, you can set the translation options to each field individually;
3. Set the fields either to "copy" or "translate", depending on how you wish them to behave.
There are many fields that need proper setting. Please go through them carefully. I attached two images with examples of what I'm referring to. Please notify me after setting it, updating the original and the translations again if it behaves as you expect. Again:
Important notice: please note that there's custom CSS that is not working across languages. I couldn't find how the custom CSS that removes the shadows was implemented. To fix that, you can add this CSS in Appearance > Customizer > Custom CSS, so it gets recognized in all languages. Please check the implementation to see if the CSS selector matches what you need.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.