[Resolved] oceanWP WPML translating Footer and Header
This thread is resolved. Here is a description of the problem and solution.
Problem:
It is currently not possible to translate the Ocean WP Footer Template created inside of the Theme Library.
Solution:
Our compatibility team provided a fix that will need to be implied by the theme author into their theme:
Set the custom field ocean_custom_footer_template to copy-once and update the page and its translation.
Go to plugins/ocean-extra/includes/metabox/metabox.php
Find
so i'm trying to translate my elementor footer template for my OceanWP child theme.
Even though the strings are translated, the template itself (footer template library ID) is not updated when switching between language.
I've read a bunch of topics about this issue but i can't make it right mainly because i can't find the right domain and the right string in WPML > String Translations.
In the domain list, i don't have any "admin_texts_theme_mods_oceanwp".
My child theme is named "eltonology" but i can't find any "admin_texts_theme_mods_eltonology " either.
thus, i can't find those strings to update the template ID :
[theme_mods_oceanwp]ocean_footer_widgets_template
[theme_mods_oceanwp]ocean_header_template
So i did click on the link "Translate texts in admin screens"
there, i did find those 2 :
theme_mods_eltonology
theme_mods_oceanwp
but even if i click on the "+" and save, i cant' figure out what to do next as i still can't find the previous strings.
My problem is, that I am not familiar enough with this theme and I tried to set up a footer that will not be visualized on my test page. Could you please check if I missed something and let me know if the same issue occurs on this test site?
Hi Andreas,
If i understand well, I've linked the footer to the website by going to the customizer and "footer widgets" and then i've selected the template there. Now the footer shows up everywhere on the website. Is that what you needed ?
I actually tried to use the backend theme options but they seem not to work as expected.
I then tested and it was kind of tricky to translate the footer. First of all, I got to tell that the translation works once the plugin "Ocean Extra" is disabled.
Now, in order to translate the footer, I first had to duplicate the original footer, and then edit the translation manually (translate independently to cancel the connectivity as duplicate).
Then I tried to translate the Shortcodes using the WPML Translation Editor and after that, I was able to see the admin text entry on String Translation to translate the ID only.
Here some more detailed steps:
1) Go to Theme Library
2) Select Footer in the default language
3) In the right sidebar, language options mark the checkbox "Duplicate" then create the translation.
4) Change the language in the top admin bar to one of the duplicated translations.
5) Take note that those duplications are connected with the original page. On the top of the right sidebar, you should see now an option "Translate independently". Click it and then edit the Footer into the respective language.
6) Go back to the Theme Library and take note of the shortcode for each footer.
7) Now translate the default language footer using the WPML Translation Editor and replace the correct shortcode for each language.
8) Finally, go to WPML -> String Translation, select admin_texts_theme_mods_oceanwp from the domain filter dropdown and you should see some entries that only show a number. This refers to the ID of each shortcode. Translate here the ID only.
9) Disable Ocean Extra Plugin, translations worked on my test.
Please let me know if you experience different results on your live site. How does it behave if you use Elementor Templates instead, would this be an appropriate workaround in the meantime?
I am escalating this issue to our compatibility team and I will follow up with you as soon I receive more feedback.
First let me thank you for all your efforts of this matter !
OK, a lot of infos here 🙂
1) I can't disable "Ocean Extra", it's an active part of the theme. No more "Theme Panel" (and library) without that. Look, it's gone on your test site 🙂
2) The thing that confused me the most is why you have the "admin_texts_theme_mods_oceanwp" in the domain list and i don't !
Is it because you first did the duplication step and then used the WPML Translation Editor ?
3) You're right, may be it's just a problem with the way the footer template is handled by OceanWp so i can use an Elementor Template for the Footer instead if i can't make it work. The result would be the same anyway. I'll see if it's only "footer" related cause the other templates in OceanWP's Library are used as hooks (something Elementor can't do by itself).
Our compatibility team will work on a solution and I will be in contact asap.
Onwards your questions:
1) I can't disable "Ocean Extra", it's an active part of the theme. No more "Theme Panel" (and library) without that. Look, it's gone on your test site 🙂
I understand. In fact, on the test site, it is working as I disabled Ocean Extra, which makes me wonder why this works if the plugin is supposed to be responsible for the library. I guess our team will be able to fix this soon and I will provide the workaround. We might also try to reach the theme author in order to implement changes.
2) The thing that confused me the most is why you have the "admin_texts_theme_mods_oceanwp" in the domain list and I don't!
Is it because you first did the duplication step and then used the WPML Translation Editor?
Exactly, I also think this should work after duplicating the Library Template. Please let me know if it worked out. Try to follow my exact steps. In fact, I am unsure if it is really necessary to set Library as translatable and use the WPML Translation Editor, as in the end, I had to use String Translation to translate the ID anyway.
3) You're right, may be it's just a problem with the way the footer template is handled by OceanWp so i can use an Elementor Template for the Footer instead if i can't make it work. The result would be the same anyway. I'll see if it's only "footer" related cause the other templates in OceanWP's Library are used as hooks (something Elementor can't do by itself).
Indeed, I think it might be an appropriate workaround for the meantime until I can provide a workaround for the theme library. Let me know if you run into any issues.
Hi Andreas,
Thanks a lot for getting back to me of this matter !
So i've made the edit on the metabox.php and now it's working as expected.
You're the man, thank you !
So i guess, no more update of the "Ocean Extra" plugin without that patch 🙂
Did you reach the author about this problem ? Just to know if it might be fixed someday or if i'll have to apply the fix everytime.
I have to give credit towards our compatibility who had a fix ready in no time.
We will further try to reach out to the plugin author in order to implement the changes into his next plugin update, as if those edits will not be taken into consideration, the upcoming plugin update might overwrite our fix again.
If possible, I would further suggest you additionally reach out to the OceanWP support and explain the issue, as I did not receive any feedback yet about if we were able to reach the author.
