[Resolved] visual product translator not working and not including slug
This thread is resolved. Here is a description of the problem and solution.
Problem: When attempting to translate a product using WPML, two issues occur: 1) slug translation is not available, and 2) every other attempt results in only code translation being available, not visual. Solution: The issue is identified in the file
. It involves a function that loads translation jobs, which interacts with another process in WPML, causing the problem. A temporary workaround involves commenting out specific lines in the mentioned file to prevent the issue. However, our developers have currently decided not to permanently fix this issue due to past complications with the wpautop function. If more reports arise, they may reconsider.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance 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.
Background of the issue:
Hello
When I want to translate a product via WPML translator
1. slug translation is not proposed
2. every 2 times, roughly, only code translation is available, not visual one
Symptoms:
This roughly happens every 2 times for code / visual
Systematically for slug
Hi,
I traditionnally only use classic translation editor.
But now need also wordpress editor, since I can't write in HTML
As you will see, the "visual" windows are empty ... only code is accessible
The slug translation is also missing
Kind regards
Hi,
1. use Advanced Translation Editor. Not interested.
2. Outdated
3. had tried, did not work. It may work sometimes when reloading the pages, but is anyway a waste of time and resource, for each product x each translation ...
So, I just tried.= 5. No effect.
not sure that the issue is from TinyMCE ... seems more to be WPML's
Attached, an image with the original text / code of a given product. It's "normal".
If I look at the version to be translated in WPML it's different. There are <p> </p> added .... which are not in original version. TinyMCE doesn't work with blocks.
And last, the slug is not proposed for transalation.
The issue you're encountering is related to a bug in WordPress Core, not WPML. Like many other plugins, we use the TinyMCE editor, which is still included in WordPress even if you're using blocks. Other plugins also rely on this editor. Our suggested workarounds aim to bypass this core issue.
If you need further assistance, I recommend posting your issue in the WordPress core ticket: https://core.trac.wordpress.org/ticket/53644 or trying the last workaround mentioned there by one of our own developers. You can also find numerous reports about this issue hidden link">here.
Regarding the slug:
Regarding the slug translation: If you'd like to translate your product slug using the WPML Classic Translation Editor, you'll need to enable this option under WPML -> Settings -> Translated Documents Options. Change the setting from "Auto-generate from title (default)" to "Translate (this will include the slug in the translation and not create it automatically from the title)".
Hi,
Sorry, I don't understand, since it's just about ... suppositions, rather than facts.
Who is adding the <p> </p>?
If this is WP, though they are invisible on my side and site on whichever product, could you precise where it does come from and explain factually how this could be generated by WP / Woocommerce?
Regards
I'm talking about the "Visual" Mode not showing anything, and that's a caused by an unsolved WP core ticket.
If you are getting p Tags added, please provide me with an isolated staging environment where only WPML, WooCommerce and WooCommerce Multilingual are active so we can isolate and reproduce the issue.
Please also try first to increase your WP_MEMORY_LIMIT to min. 128MB, as your setup is running below system requirements for WPML and WooCommerce (not PHP_Memory, that's enough bot your WP_MEMORY_LIMIT defined as constant in WP_MEMORY_LIMIT)
I changed the wp-memory limit to 128. No effect. What is logical since I never got memory exhausted or whatever like this.
Now, fact is that visual translator works ca every 2 times. So, it's not always, and it's not never. How could you relate this to "an unsolved WP core ticket", which is 3 years old, while the problem I am reporting is recent. I think since WPML included a wordpress translator.
Re. the p tags, sometimes there are present, sometimes not. And anyway, they are never in original product (in WC), they are only in WPML translator. So, logically, they can't be added by WP / WC, only by WPML, you have the facts.
For you, there is no relationship between the 2 events. It's a guess without fact.
For me, since they coincide, are concomitant, I believe the opposite. There are 2 "things" where the behavior is sometimes "yes", and sometimes "no".
Finally, I have a staging site, which you can use freely.
I changed the wp-memory limit to 128. No effect. What is logical since I never got memory exhausted or whatever like this.
The site currently requires a minimum of 141MB of memory. You can view the current usage here. Please note that this increased memory requirement is not only due to WPML but also required by plugins like WooCommerce.
Regarding the p Tags:
Re. the p tags, sometimes there are present, sometimes not. And anyway, they are never in original product (in WC), they are only in WPML translator. So, logically, they can't be added by WP / WC, only by WPML, you have the facts.
From what I can see, when you open a product like hidden link">this one, you can see the <p> tag in the "Contenu / Description" field. It disappears when you switch between "Visual" and "Text" modes. I can reproduce this behavior on every page refresh.
I will check the database and get back to you.
Regarding the "Visual Mode"
Since the visual mode seems to be functioning, you won’t need the workaround I mentioned earlier. I suggested it because your screenshot showed an empty 'Purchase Note' field, which is typical for this issue. However, the field was indeed empty in the product itself, so it doesn’t seem to be related to the <p> tag issue. Unless you've noticed any specific products where the 'Visual' mode is always empty and the content only appears in the 'Text' mode. If yes, please let me know.
