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.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Background of the issue:
I'm using 2 slider revolutions on a page. Slider revolution uses a shortcode
en:[rev_slider alias="intro-1"][/rev_slider]
es:[rev_slider alias="intro-test-1"][/rev_slider].
When I'm translating a page, it does not show me a field for a shortcode. I'm inputting a slider revolution to ES version manually in Elementor, but every time somebody updates a site it resets to EN version.
Symptoms:
Shortcodes are not translating, and the ES version resets to the EN version after updates.
Questions:
Why does the ES version reset to the EN version after updates?
How can I ensure the shortcode field appears when translating a page?
While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly.
That is expected, as you should not mix translation methods, you should either use a manual method or the WPML ATE editor. Mixing will overwrite each other.
1) I suggest following our guide and translating the Revolution slider as in our docs if you are using Wthe PML ATE editor:
2) Otherwise you can switch to WP editor and add manual translation, and edit 2nd language page how you wish. Note re-enabling and doing translation via WPMl ATE again, will overwrite manual changes done.
I hope you're doing well. I've taken over this ticket and will be happy to assist you in this matter.
I understand your query. Please note that the ATE is designed to display only translatable strings. When using ATE for translation, HTML tags or shortcodes are stripped out, and only the text content is sent to the translation editor. If a shortcode has WPML support for any of its attributes, the values of those attributes will also appear in the editor for translation.
On the other hand, the CTE can display all content, including shortcodes, by default, as it is parsed through the rich text editor. The translation fields in CTE also support a rich text editor, allowing you to adjust the formatting as needed. I hope you can understand.
To translate the Revolution Slider shortcode, please refer to the guide below and ensure the shortcode attribute is registered for translation.
Once the shortcode is registered for translation, make a small edit to the page containing the shortcode and save the changes. Then, update the translation. The attribute value should now appear in the translation editor. Add the required translation for the attribute value, and save the changes. In this way, you can translate the attribute of the revolution slider shortcode and display the slider as per your needs.
You can also translate the entire shortcode from String translation if you want.
I hope I was able to clarify things for you. Feel free to reach out if you need further assistance or additional clarification. I’ll be happy to help!
