This thread is resolved. Here is a description of the problem and solution.
Problem: The client was inquiring about different methods of translating layouts in Divi Builder using WPML, the possibility of using the Divi visual builder for layout translations, translating taxonomy slugs to keep the same slug across languages, and forcing the default language to include the language code in the URL.
Solution: 1) We recommend not mixing different translation methods for the same item. If you're using the WPML translation editor, directly editing the translation can lead to problems. More details can be found here: Using different translation editors for different pages.
2) It is expected behavior that the Divi visual builder cannot be triggered while translating layouts because the "edit with the Divi builder" button does not appear in this case.
3) To keep the same slug for translated taxonomy, you need to enable the slug option in the WPML settings. Please refer to this documentation: Translating taxonomy slugs with WPML.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues at WPML known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, 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.
The procedure is translate management > layout selection > translate yourself > go to the translation tab > find the layout again > translate it
However, I tried also a different method, quicker that is simply:
translate management > hover on the layout to translate > click on "Edit" > translate in the language of interest
Two questions:
1) There is any reason why I should not use the latter method that is faster?
2) Regarding the latter method I noted that, in constrast to post, the translation with the wordpress editor doesn't allow to enable the visual builder. If click "copu content from default language", the code related to divi block show up, but there is not way to interpret that code with the visual builder as it is possible to do in the posts. So, I can translate the layouts only by using the WPML editor. However I prefer the wordpress editor for translation, so there is any change to activate the divi visual builder on layout as well?
1) There is any reason why I should not use the latter method that is faster?
It seems to me that you are creating the translations manually. Please note that it is not a good idea to mix different methods. That means, if you are using the translation editor, directly editing the translation can lead to problems.
2) Regarding the latter method I noted that, in constrast to post, the translation with the wordpress editor doesn't allow to enable the visual builder.
Once a post is copied, you can edit via WordPress editor or via Divi Builder, just as you can do with posts in the original language. Does that answer your question? I might not have quite understood your question.
1) no, my method "translate management > hover on the layout to translate > click on "Edit" > translate in the language of interest" make use of the WPML translation editor. However instead passing between two sections ("translation management" and then "translations") I found quicker to edit layout translations of layout in that way. I was just wondering if it is ok, or should I use the longer method described in your documentation (management > layout selection > translate yourself > go to the translation tab > find the layout again > translate it).
Why it is not a good idea using different editors for different pages or post? I did not find an answer about that in your docs. In my case, I use to translate all posts using the wordpress editor, and some pages with the WPML classic or advanced editor. I did not have any issues so far. I like the wordpress editor because maybe in the future I will be able to quickly download all posts in all different languages.
2) No, I mean that when I translate posts with the wordpress editor, I'm able to trigger the divi visual builder, while it is not possibile to trigger it while translating the Layouts (Divi builder theme layouts) because the button "edit with the divi builder" doesn't show up in this case. I was wondering if this is a normal behavior or something is not working from my side.
3) An additional question regarding taxonomy translation.
In my case I have the category "blog". WPML automatically change it to blog-es for the spanish version, but I want to keep "blog". In a post (https://wpml.org/forums/topic/category-translation-slug/) I read that it is possibile to do it, but I did not find a solution, as it changes each time I try to save it as "blog". How to do it?
4) How to force the default language to add the language code in the url? E.g. mysite.com/en instead of mysite.com.
1)
It is ok to translate that way, it's also an available option from WPML. No problems here.
It is also ok to translate some posts/pages with the translation editor and others with the WordPress Editor. What can lead to issues is translating the same post using different methods, e.g., you start translating a post with the translation editor and then edit the same post manually using the WordPress editor. That could be problematic.
2)
That's expected behavior from Divi. Every theme has its particularities and WPML handles them differently.
thank you. regarding categories slug I tried to turn off in Yoast SEO ""Show the categories prefix in the slug". However it generated for the translated language 404 errors.
I created a new ticket to handle this 404 issue. Since it's a bit more complex, it's better to analyze them separated from your other questions. I'll answer you there 🙂
