Open raykai opened 4 years ago
I got unfortunately mislead by a post on WPML about it's compatibility two years ago and got Oxygen because of this.
I don't think that Oxygen team will be doing must about this after all this time of inaction.
I do not suggest to buy this page builder if you need 100% translations functionality. So if you are checking before you buy, please check the first link below and make your decision after. They are some work around but there is other issues that come with this when updating site content particularly.
I did get good support form WPML as they tried hard to find some solutions.
We're sorry but we could not get cooperation from the Oxygen developers on this issue.
We mention the following here.
https://wpml.org/documentation/plugins-compatibility/oxygen-visual-builder/
Please note that Oxygen Builder is currently not compatible with WPML. We reached out to their team to fix the current issues related to translating the content built using Oxygen.
If you need to use Oxygen with WPML, we suggest reaching out to their team and asking them to work with us on fixing the current issues. One of the ways of doing this is by upvoting and commenting on the open issue on the support page they already have for this.
Voting for full compatibility ASAP with WPML.
I am from the DIVI ( Bloated) world and am looking forward to have a good page builder like Oxygen compatible with WPML.
For does looking for some help on the subject:
- https://wpml.org/forums/topic/oxygen-builder-translation/#post-8434339
- https://wpml.org/documentation/plugins-compatibility/oxygen-visual-builder/#translating-oxygen-reusable-elements-templates
For WPML config file to get some fields into translation:
<wpml-config>
<shortcodes>
<shortcode>
<tag>oxy_rich_text</tag>
</shortcode>
<shortcode>
<tag>ct_link_text</tag>
</shortcode>
<shortcode>
<tag>ct_link_button</tag>
</shortcode>
</shortcodes>
</wpml-config>
IF any body knows how to get the link to translation in any modules with links that would help! Maybe a attribute tag?
Thanks!
Having to choose between WPML and Oxygen, I choose the later one. Oxygen builder is the best builder with amazing SEO results. WPML is buggy regardless of the builder.
On 11 Jan 2023, at 11:12, MarcLob @.***> wrote:
I got unfortunately mislead by a post on WPML about it's compatibility two years ago and got Oxygen because of this.
I don't think that Oxygen team will be doing must about this after all this time of inaction.
I do not suggest to buy this page builder if you need 100% translations functionality. So if you are checking before you buy, please check the first link below and make your decision after. They are some work around but there is other issues that come with this when updating site content particularly.
I did get good support form WPML as they tried hard to find some solutions.
Just got an email today from WPML about this and almost 2 years after posting on this support issue...
We're sorry but we could not get cooperation from the Oxygen developers on this issue.
We mention the following here.
https://wpml.org/documentation/plugins-compatibility/oxygen-visual-builder/
Please note that Oxygen Builder is currently not compatible with WPML. We reached out to their team to fix the current issues related to translating the content built using Oxygen.
If you need to use Oxygen with WPML, we suggest reaching out to their team and asking them to work with us on fixing the current issues. One of the ways of doing this is by upvoting and commenting on the open issue on the support page they already have for this.
938 https://github.com/soflyy/oxygen-bugs-and-features/issues/938
Voting for full compatibility ASAP with WPML.
I am from the DIVI ( Bloated) world and am looking forward to have a good page builder like Oxygen compatible with WPML.
For does looking for some help on the subject:
https://wpml.org/forums/topic/oxygen-builder-translation/#post-8434339 https://wpml.org/documentation/plugins-compatibility/oxygen-visual-builder/#translating-oxygen-reusable-elements-templates For WPML config file to get some fields into translation:
oxy_rich_text ct_link_text ct_link_button IF any body knows how to get the link to translation in any modules with links that would help! Maybe a attribute tag?
Thanks!
I got unfortunately mislead by a post on WPML about it's compatibility two years ago and got Oxygen because of this.
I don't think that Oxygen team will be doing must about this after all this time of inaction.
I do not suggest to buy this page builder if you need 100% translations functionality. So if you are checking before you buy, please check the first link below and make your decision after. They are some work around but there is other issues that come with this when updating site content particularly.
I did get good support form WPML as they tried hard to find some solutions.
Just got an email today from WPML about this and almost 2 years after posting on this support issue...
We're sorry but we could not get cooperation from the Oxygen developers on this issue.
We mention the following here.
https://wpml.org/documentation/plugins-compatibility/oxygen-visual-builder/
Please note that Oxygen Builder is currently not compatible with WPML. We reached out to their team to fix the current issues related to translating the content built using Oxygen.
If you need to use Oxygen with WPML, we suggest reaching out to their team and asking them to work with us on fixing the current issues. One of the ways of doing this is by upvoting and commenting on the open issue on the support page they already have for this.
938 https://github.com/soflyy/oxygen-bugs-and-features/issues/938
— Reply to this email directly, view it on GitHub https://github.com/soflyy/oxygen-bugs-and-features/issues/938#issuecomment-1378812565, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQC4BHDGW4FF7UL3Y3TDT7DWR25TRANCNFSM4LZBCWYQ. You are receiving this because you commented.
+1 for better polylang or any WPML
WPML, polylang and translatepress should work fully
+1 for WPML and polylang
+1 for WPML and polylang
+1 for WPML and Polylang support. Oxygen is an amazing tool, but at the same time Multilanguage is crucial in many cases.
WPML, we need this support for Oxygen as Oxygen is stronger and better every day.
+1 Support Oxygen for WPML plugin!
+1 as you know WPML wants to work with you to solve the problems.
+1
@Qbaska it is sad at same time, to ignore the demand of so many users.
Anyone who has had trouble with WPML and Oxygen should try 4.6 RC 1 from https://oxygenbuilder.com/portal.
I just translated a WooCommerce product/shop with no trouble at all: https://www.loom.com/share/748d80f59d2744f38d604f656b221490
There may still be edge cases, but compatibility is vastly improved in 4.6 RC 1.
Anyone who has had trouble with WPML and Oxygen should try 4.6 RC 1 from https://oxygenbuilder.com/portal.
I just translated a WooCommerce product/shop with no trouble at all: https://www.loom.com/share/748d80f59d2744f38d604f656b221490
There may still be edge cases, but compatibility is vastly improved in 4.6 RC 1.
haha so its not there but its there... crazy and funny. and fits very well to the whole oxygen situation. i really wish all good luck.
I was positively motivated at start with Oxygen, gave it all the good will and tests. But after two years of no developments, no news about it, if any support for WPML was in dev and following this thread, I came back to Divi. Too bad guys! You had something good there!
Just published two days ago (April 24th, 2023): https://oxygenbuilder.com/category/releases/
Is it possible to translate buttons now?
another fun fact. they now suggest to use a RC version. which still don't even offer an official support for wpml....
another fun fact. they now suggest to use a RC version. which still don't even offer an official support for wpml....
I believe what @Spellhammer was suggesting is that things slowly are moving towards better compatibility. So lets give this a chance. Im sure in less than a month or so the beta will be public. So we can test it meanwhile. No one said to use it in production.
Oxygen RC versions are stable enough for use in production.
Oxygen RC versions are stable enough for use in production.
@Spellhammer is it possible to translate buttons now?
Oxygen RC versions are stable enough for use in production.
@Spellhammer is it possible to translate buttons now?
He clearly showed in the video on Loom, that its in WooC. You may try to find button text in String Translation in WPML for WooC and translate it there.
Oxygen RC versions are stable enough for use in production.
@Spellhammer does it update now the translation of pages properly?
I want to use WPML in a website made with OXYGEN. It is written HERE that OXYGEM is compatible with the WPML. Please solve all issues soon, because this creates serious problems in our work. Thank you.
I want to use WPML in a website made with OXYGEN. It is written HERE that OXYGEM is compatible with the WPML. Please solve all issues soon, because this creates serious problems in our work. Thank you.
This info is true till version 4.6 RC (beta). https://oxygenbuilder.com/2023/04/24/oxygen-4-6-rc-1-now-available/ I would do a full test before engaging a new site for a customer.
As for WPML, till now (before v4.6RC), they do not consider Oxygen compatible: https://wpml.org/documentation/plugins-compatibility/oxygen-visual-builder/
What is the current state concerning Oxygen and multi-lingual websites?
The European Union has 24 official languages in 27 member states that resemble together a unified market of 446 million people (USA: 333M). Anyone serious about doing business and commerce throughout this huge market absolutely depends on multi-language support of his website builder.
This feature request is 3 years and 1 month old. Over 100 users have upvoted it. Until recently people write about it in a way that it seems that the feature still is not in place. I can't find this topic on the Oxygen roadmap, not even under "Good Ideas".
On the Oxygen website I can read this, updated March/2022: "Oxygen has rudimentary support for WPML, Polylang and Weglot. This is not an official feature of Oxygen and no support will be provided via official support channels. Note that the Oxygen and WPML teams have been in contact and are jointly investigating official compatibility. This does not mean that WPML compatibility is planned or guaranteed at this time. Information on translating content created in Oxygen can be found on WPML's website."
Following that link to the WPML website I read this, updated Oct/2022: "Please note that Oxygen Builder is currently not compatible with WPML. We reached out to their team to fix the current issues related to translating the content built using Oxygen. If you need to use Oxygen with WPML, we suggest reaching out to their team and asking them to work with us on fixing the current issues. One of the ways of doing this is by upvoting and commenting on the open issue on the support page they already have for this.", which links to this page here on Github.
So it seems that the WPML team tried to make it happen together with the Oxygen team, but Oxygen denied to work together with them and does not even plan to support it ever? And now both companies are pointing fingers at each other?
@Spellhammer , @Kpudlo , @KittenCodes please provide transparency about what the plans of Oxygen are concerning supporting WPML or any other multi-language support and especially what the current state of implementation is, if any, including an outlook for at least a roughly estimated ETA for this feature.
We need to take business decisions based on this, since we would like to change to Oxygen, but language support is a must-have for us, as for many other European companies. Thanks for any information on this!
+1 @Tom-H-L
Translatepress makes it seem here like it works 100% out of the box with Oxygen. Can someone confirm this? I can't find any information on the Oxygen website about this. Or suggest any other multi-language plugin that works with Oxygen?
The only thing that stops our agency to switch to Oxygen is lack of support of multilanguage feature. As 90% of our clients demand websites to be available in German and English, the WPML plugin is a must, thereby we have purchased the most expensive license. Sad that for a few years, there is no big update from Oxygen team, we have to stick to other tools and builders. We seriously need a multi-language support (WPML).
@Mamadzhanov the level of ignorance practiced here, is one of high skills. At first the founder of Oxygen, made a promise that WPML is supported, in a youtube video, 7 years later we all know is working yet with very many downsides, and that promise turned into dust.
Now they made a fix no one knows what exactly, since that was reverted. So in fact they made more dust. No real changes in WPML + Oxygen for years.
@Spellhammer @louisreingold any comments on this matter? Here is the misleading video, I am sure they forgot about it, and maybe will better remove the video, since thats a false promise they made there.
@uhlhosting
We stand by our comments in this thread and what is written in the documentation at https://oxygenbuilder.com/documentation/other/multilingual-with-wpml/.
The video you link to is clearly says "beta" and was also for Oxygen 1.x, which was completely discontinued many years ago. 2.x was a rewrite and is not backwards compatible. None of the documentation or videos for 1.x applies to 2.0 and beyond at all.
@louisreingold Thanks for joining the discussion.
Can you please give guidance / informormation on this, so that we can estimate how good Oxygen would work for multi-linguage sites, as this is mission critical for us:
Translatepress makes it seem here like it works 100% out of the box with Oxygen. Can someone confirm this? I can't find any information on the Oxygen website about this. Or suggest any other multi-language plugin that works with Oxygen?
@Tom-H-L I have regularly used Oxygen Builder and Translatepress together on dozens of sites over the past 2 years. Everything can be translated. Maybe sometimes you need to do some editing in the original blocks to get them recognized. For example, changing form type (from text to rich-text and vice versa) or packing elements into divs or spans... In the end, however, everything can be translated.
Rather I found some issues between Translatepress and other plugins, like CPT UI archives, CF7 email, search and filter plugins...
Having a frontend approach the translation is quick and easy, but the management is lacking compared to WPML. But the comparison between the 2 is another matter...
With WPML you can't translate buttons created in Oxygen Builder. That makes it useless.
@spinoWeb2
@Tom-H-L I have regularly used Oxygen Builder and Translatepress together on dozens of sites over the past 2 years. Everything can be translated. Maybe sometimes you need to do some editing in the original blocks to get them recognized. For example, changing form type (from text to rich-text and vice versa) or packing elements into divs or spans... In the end, however, everything can be translated.
Thank you for that information, much appreciated! So as it seems, due to Translatepress, someone CAN use Oxygen for multilingual websites. This brings Oxigen for us back in the game, we had eliminated it from the short list of possible solutions already due to the suspected non-compatibility with any multilingual plugin.
Having a frontend approach the translation is quick and easy, but the management is lacking compared to WPML. But the comparison between the 2 is another matter...
I thought of this, but since we need Wordpress only for small portfolio sites, I guess that the frontend approach remains maintainable, now? We need this sites to be multilingual and SEO optimized. Translatepress works fine for SEO, too, no?
Recently I made a site with polylang and it worked mostly fine (you have to remeber about not allowing to synchronize custom fields)
Since I don't want to copy/paste every text field from a page to another inside the Oxygen Builder, I just made a very simple python script to automate at least the translation process. (you will keep doing copy paste between the JSON of a page to the JSON of the translated page) Hope it helps someone. https://gist.github.com/pad52/06938927329125a08ff4af474e4a60f2
Please, can someone make a little tutorial or write in bullet list how to translate pages with Oxygen, and with what plugin?
Hi, I'm writing this (I hope) short tutorial to illustrate the process that I and my web agency are using to integrate wpml with oxygen.
First of all I confirm that the translation of the pages and all post-types will necessarily be a manual translation. I will divide the tutorial into two parts: The first for templates and the second for pages and all post-types.
My goal was not to duplicate each template and then associate it with each translated page. So I solved it like this:
Install the code snippet plugin and insert this php code, This allows me to add a conditions to oxygen and be able to select in the templates what to display in different languages.
// WPML condition
if (function_exists('oxygen_vsb_register_condition')) {
$lang_list_full = icl_get_languages();
$lang_list = array();
foreach($lang_list_full as $code) {
$lang_list[] = $code['code'];
}
oxygen_vsb_register_condition(
//Condition Name
'Language',
//Values
array(
'options' => $lang_list,
'custom' => false
),
//Operators
array('==', '!='),
//Callback Function
'wpml_callback',
//Condition Category
'WPML'
);
function wpml_callback($value, $operator) {
$my_lang = ICL_LANGUAGE_CODE;
global $OxygenConditions;
return $OxygenConditions -> eval_string($my_lang, $value, $operator);
}
}
Open a template, duplicate the element you want to translate (heading, text etc...)
Now put a conditions for each item to display for each language. Here is a screenshot
Now you have unique templates and no longer need to duplicate them for all languages
For pages, however, the method is similar to the guide on the wpml forum. But I'll give you the points you follow here:
For now I also update all the button links in the translated pages, I don't know if there is an automatic way with wpml to translate the links.
I know it's complex but for me it's the best method if you want to use wpml and oxygen.
I hope this can help you.
I developed some tools for partially automate the translation process of oxygen websites with wpml. Check it out here https://github.com/pad52/oxygen-wpml-tools
@pad52 how you handle the conditions to display the correct language on language switch?
I am translating in a similar way of @soloconfusione (mentioned here: https://github.com/soflyy/oxygen-bugs-and-features/issues/938#issuecomment-1710465734)
So I am translating templates and pages using the method (and switch) provided by WPML.
The only difference is that instead of translate manually every page or template I am using my tools to generate the JSONs out of the original JSON and a .PO file, then I paste the result in the JSON tab of the translated page/template.
I am not using the Oxygen conditions method.
@pad52 not sure I get it how would that work without the conditions, if thats possible, ohmy, lifesaver. Can you make a short video maybe on the whole process? I am sure many can benefit from it.
Unfortunately, not working anymore...
Now using per-page & per-product template setting (IT-single_product_page, EN-single_product_page to be assigned to single products & IT-contact_page, EN-contact_page to be assigned to let's say "contact" page)
Gettext php functions in code block for texts in single template archive pages (BLOG, BLOG post, 404, Search..)
I tried but cannot make conditions working...
Describe the feature you'd like to see included in Oxygen. Support for WPML https://wpml.org plugin would be good to have for Oxygen
What are the use cases for this feature? Language Accessibility
Examples of this feature or functionality. It would allow users to use more than one language on their sites when they build using Oxygen. I live in a country where we need two languages on our sites so having support for WPML is almost a must for us.