-
Posts
-
Hi,
I’ve just started translating the first few pages with WMPL and noticed that the translated words don’t show for the overlay headline on the full-width slideshow element.
Everything else translates perfectly fine (including the “Contact” button underneath the headline. What I see in the WMPL translation editor is what I see on the page.
So I’m pretty sure it has to do with theme compatibility, and not WPML.Could you please help?
Login creds and direct link to the page and translation module is in the private content area below.The website will be pretty much ‘static’ (no blog, no regular changes of content). So I guess one solution could be to create translated pages, and then fix the problem manually afterwards (editing the translated instance of the page).
Or would this lead to some sort of ‘sync problems’ between the pages and their underlying link to the WMPL plugin?Many thanks for your help!
Hey BelIblis,
Thank you for the inquiry.
We are not yet sure why the caption title is not properly translated. Have you tried to remove the slider, update the page, then add it again from scratch? As you may already know, you could also duplicate the page to another language and translate or edit the content manually instead of using the translation management.
Best regards,
IsmaelHi Ismael,
I haven’t tried removing/adding from scratch. But that would be more work than just translating it manually.
How does the WMPL workflow work? I seem to have two options here:
1) Duplicate page via WMPL translation management, followed by manual override to fix the slider headline
2) Duplicate page without WMPL translation management.Is there a difference between these two approaches? Would I run into potential problems if I use option 1?
(For example: Can I go back to using the WMPL translation manager after I’ve manually changed a page that was initially created within the translation manager?)Thank you!
Hi,
Thank you for the update.
When using the translation management, you are limited to the existing elements or shortcodes that are already included in the original page and have no way to change the layout of the translated page. You will have more control over the translated page when the translation management is not enabled because you will be able to actually use the Advance Layout Builder or the classic editor to edit the page.
Best regards,
IsmaelHi Ismael,
I had some other problems with WPML that definitely didn’t have anything to do with Enfold, so contacted the WPML support today. Which also fixed the problem here in this thread.
The culprit was Gutenberg. And I think this is important info for a lot of websites done with Enfold:
When you create the first wordpress page for a website, Gutenberg is active. When switching to the Avia builder, Gutenberg disappears, BUT(!) there’s still some invisible code from Gutenberg on the page.
So, to keep design elements and structure the same for the next page, I duplicated that first page. And again for the next page,…
The result is: That Gutenberg code is now sitting inside every page. And WMPL really doesn’t like that at all!Solution was:
– install the “Classic Editor” WordPress plugin
– get the problematic page’s post ID (hover over it & browser will display the page-id)
– in the SQL database, go to the wp_posts table and search for the post_id
– on the post_content col, remove all tags and save
– on WP, do a small modification on the original post and save
– update the translationThat fixed a lot of the issues, including the missing slider header translation. Maybe worthwhie pointing this out in your manual / the Enfold “WPML Wokflow” page.
Hi,
– on the post_content col, remove all tags and save
Does it work correctly when you remove the tags directly from the builder? After switching to the advance layout builder (ALB), the default content from the Gutenberg builder, if there are any, should be converted to a text block automatically. You might be able to just remove the content from the ALB directly instead of editing the database entry.
Best regards,
Ismael
- You must be logged in to reply to this topic.