Waiting for author
Overview of the issue
Recently, some WPML users have reported that they are unable to translate the Link field assigned to buttons, text, or other widgets via WPML’s Translation Editor.
Please note that this is not the same issue as Oxygen Builder – Completed translations do not load on the front-end. However, if you are experiencing that issue, please follow the instructions there before attempting to fix the issue outlined here.
Workaround
Next steps to resolve this issue
WPML team is jointly investigating official compatibility with the folks from Oxygen Builder to try and find a permanent solution to this issue (and the issue affecting translations not showing on the frontend). While we cannot guarantee any solution, expressing your interest in this effort to the Oxygen Builder team via their GitHub, Facebook page and/or user group can only help move things along.
Hello,
Unfortunately this solution does not seem to work on my side.
– Copied the code so is active
– Removed the content of the xml config (tested with it after)
– Created a new test page
– No link in translation
Tested with oxygen modules:
– Text link
– Link wrapper
– Button
Thanks
Thank you for reporting it Marc. Could you please provide this information in your support ticket so we can follow this situation up.
Thank you for your help.
This is not a better version of https://wpml.org/forums/topic/oxygen-builder-translation/#post-8600795 but just a workaround. Is there any solution for using WPML’s translation Editor for “ct_link_text” and “ct_link_button” shortcodes?
Hey there,
We are investigating a solution with the Oxygen Builder team. However, the best way to resolve this issue is to manually translate your content.
Don’t hesitate to open a ticket in a support forum if you need further help.
Regards
Andrés, Supongo que habla español, mi problema no es traducir manualmente, mi problema es que no muestra mi tienda cuando activo el segundo lenguaje
Gracias por la aclaración Camilo, sin embargo, no parece tener relación con el tema que se discute en esta errata.
Lo mejor es que abras un ticket en el soporte para que lo podamos investigar.
There´re plenty of errors using wpml in O2. The content is not displaying on frontpage and the shop page is empty. I´m not sure what to resolve this
Hey there,
Currently the best way to translate your site using Oxygen is proceeding manually.
If you still find issues using the manual translation, don’t hesitate to open a ticket in our support forum.
Regards
Any update on the compatibility with oxygen 4.x? Is this issues still being worked on? We currently would love to use WPML but unfortunately it does not work with Oxygen unless we do it manually. Since we always aim for the best possible solution, is there any roadmap to implement this feature?
Hello there,
At the moment, manual translation keeps being the best way to translate Oxygen. There has been some progress but the integration is not ready and it will still take a while.
We don’t have an ETA but we will keep this page updated whenever there is any news.
Hi WPML team,
I’m Adonay from Kademar.
We noticed this errata because we have been working on the same Oxygen + WPML frontend translation issue.
We built an independent connector, WPML Oxygen Connector, which reads Oxygen’s builder data, registers translatable content through WPML String Translation, and renders translated Oxygen content on the frontend while keeping the original layout intact.
It was created specifically for agencies maintaining multilingual Oxygen websites where manual translation or duplicated layouts are not a reliable workflow.
This is not an official WPML/Oxygen integration, but we would be happy to share technical details or provide access for review if it can help move this compatibility issue forward.
Product page:
https://www.kademar.io/en/wpml-oxygen-connector
Documentation:
https://www.kademar.io/en/documentation-wpml-oxygen-connector/
Best regards,
Adonay
Kademar
Hi Adonay,
Your connector looks promising, and it may be helpful for other Oxygen users who are facing similar issues.
I believe you are already in contact with our Partnerships team, so the conversation can continue internally from there.
Thanks again for reaching out and for sharing the details.
Hi,
Thanks for your reply and for the kind words.
Yes, I’m already in contact with the Partnerships team, so I’ll continue the conversation internally from there.
I built WPML Oxygen Connector because I’ve been using Oxygen for around six years, and I couldn’t find a reliable solution for this workflow. For agencies and site owners who already have Oxygen websites and want to keep using WPML, manually duplicating layouts or maintaining translations outside the builder is simply not sustainable in real projects.
My goal is to help make the Oxygen + WPML workflow easier and safer for users who rely on both tools, while keeping the original Oxygen layout intact.
Thanks again for taking the time to review it.