Oxygen Builder widget and link translation issues

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

We are investigating a solution with the Oxygen Builder team. However, for now, the best way to resolve this issue is by following the instructions to manually translate your page or post.

After you’ve manually translated the page/post, you can then adjust the link from within the translated page/post.

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.

10 返答へ “Oxygen Builder widget and link translation issues”

Marc De Gagné と言う：

4月 27, 2021 at 7:46 pm

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

返信
- Andrés と言う：
  
  4月 28, 2021 at 5:26 am
  
  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.
  
  返信
marcoM-116 と言う：

十一月 6, 2021 at 12:44 pm

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?

返信
- Andrés と言う：
  
  十一月 8, 2021 at 7:28 am
  
  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
  
  返信
  - Camilo と言う：
    
    2月 16, 2022 at 2:16 pm
    
    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
    
    返信
    - Andrés と言う：
      
      2月 17, 2022 at 7:01 am
      
      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.
      
      返信
soniaG-8 と言う：

2月 15, 2022 at 1:57 pm

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

返信
- Andrés と言う：
  
  2月 16, 2022 at 6:49 am
  
  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
  
  返信
michaelT-122 と言う：

10月 16, 2024 at 11:17 am

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?

返信
- Andrés と言う：
  
  10月 17, 2024 at 5:15 am
  
  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.
  
  返信