I have uploaded the template in the staging site. translateded as you said.
it is All Altawailcourses cateogy pages
now this template is getting a divi layout [Course _loop _layour_for_cat], which has 2 buttons.
view post btn , which is not getting seen by wpml at all
and a usual button , which got translated, but still was not shown in the final result of the template or live page
[ check the attached images]
very important question ! after going to translate dashboard. what should I choose.
- Theme Builder Items ( it gave me code to translate)
- I guess this Divi Body Templates but there are two options of Theme Builder Layout, should I translate these , it did not show me important parts
could you please explain with steps how this category is set to use that template and the layout?
At the moment, I’m not seeing any clear connection or assignment of this layout to the category on your site.
Please try to describe the exact steps in simple way (where you set this and how), as it’s not clear from your previous reply. Once I understand your setup, I’ll be able to check it properly.
Translation fixed for tabs but distoried the body and brings the code,It should not show the html code. only the translated text storied in the database (ACF fileds)
this is the template all altawailcourses.
So I am getting diffrent problems based on what the template contatin
Previously, the issue was that the tabs were not available for translation. Now the tabs can be translated, but the HTML tags are displayed on the front end instead of being rendered properly.
The content is coming from an ACF rich text/enhanced text field. It looks like WPML is now making the field translatable, but the translated content is being escaped or treated as plain text rather than HTML.
Could you please check why the HTML tags are not rendering after translation?
From what I can see, you’re using Divi Machine to assign the layout, and that layout is not being correctly assigned in translated template.
Since Divi Machine is not officially compatible with WPML, issues like this can occur. We can try to investigate and help, but in the end it may require collaboration with the plugin authors to ensure full compatibility.
Could you please use this sandbox and recreate a simple example similar to your setup (template with layout assigned)
- hidden link
Once done, we’ll check and try to assist further, but please note we cannot guarantee a full solution in this case.
Alternatively, I recommend also contacting the plugin authors to confirm if they support WPML or if they have a known workaround.
For new issues, I am not sure what approach you are using there and what is wrong, that needs to be checked sepratlty since probably your code is being broken, so please let’s focus on one issue per ticket. Once we resolve the current one, you can always open a new ticket and we’ll be happy to continue helping with any new one, for now lets please concentrate on this one. Handling multiple issues in a single ticket can cause confusion and slow things down.
here is the same issue but diffrent template , not sure if you want it in diffrent ticket.
just watch the video and decide .Name of the template is attached as image
thanks, but there is no need to repeat this , as I am already aware of the original issue and have explained why it happens.
In the translated template, Divi Engine is not loading the correct translated layout, and that is most likely also the reason why you adjusted some of the Divi settings and manually adjusted these templates.
For now, let’s please focus on the current main topic and my last reply. Please let me know:
- how it goes with the sandbox test site
- whether you managed to reproduce a simple example there
- and if you received any update from the Divi Engine plugin authors
We will still try to help from our side, but in the end this may require collaboration from the plugin authors as well, since Divi Engine is not officially compatible with WPML.
- how it goes with the sandbox test site
I could not , there are so many elements to produce the same idea
- whether you managed to reproduce a simple example there
use the stagging site
- and if you received any update from the Divi Engine plugin authors -
No
