soflyy / oxygen-bugs-and-features

Bug Reports & Feature Requests for Oxygen
https://oxygenbuilder.com/
314 stars 29 forks source link

Gutenberg Editor doesn't work with Polylang multilingual pages #718

Open JackGraal opened 4 years ago

JackGraal commented 4 years ago

Describe the bug There seems to be a problem with Oxygen being edited wit Gutenberg and having a multilingual (Polylang plugin) website.

So for example, if I do a home page template for English version (which is default language) and do another one for Polish version, the language that is not default will not work with Gutenberg editing. There's an error saying:

Your site doesn’t include support for the "oxygen-vsb/ovsb-pl" block. You can leave this block intact or remove it entirely.

So I assume that Polylang is adding the "-pl" to the oxygen slug and that's a problem. I've been working on 3 multilingual websites recently and the problem occured on all of them.

The only quick fix is to deactivate Polylang, edit the desired subpage with Gutenberg, save and then reactivate Polylang. But it shouldn't be like that :(

Have you tried all the steps at https://oxygenbuilder.com/documentation/troubleshooting/troubleshooting-guide/? Yes

Are you able to replicate the issue on a Sandbox install at https://oxygenbuilder.com/try? Yes, here's the link to the page with error: http://festive-jay.w6.wpsandbox.pro/wp-admin/post.php?post=65&action=edit

To Reproduce Steps to reproduce the behavior:

  1. Install Polylang plugin and create at least 2 languages.
  2. Add two pages in two different languages and link them to be multilingual with Polylang
  3. Edit those pages with Oxygen so there's some content on them.
  4. Having Oxygen Gutenberg plugin activated, make those 2 pages Gutenberg editable.
  5. Now, try to edit (with Oxygen's Gutenberg) the page that is not in default language.
  6. The error will be shown in the Gutenberg Editor.

Expected behavior Should show the Gutenberg Editable Oxygen content for all pages that have that feature active on them - regardless of their language set by Polylang.

What actually happens An error is shown in th Gutenberg Editor area.

Screenshots See the error here

Desktop (please complete the following information):

lhoucinecherif commented 4 years ago

same issue, not resolved yet.

aljazbz commented 4 years ago

Please fix this.

amaccone commented 3 years ago

Same problem here, with Oxygen 3.5, Oxygen Gutenberg Integration 1.4 and Polylang 2.8.3

DavidWooF commented 3 years ago

Is there a solution to this problem? I have the same problem with Oxigen version 3.7.1 and Oxygen Gutenberg Integration version 1.4 and Polylang Version 3.0.3

ghost commented 3 years ago

I see it's been a while since this was posted but I just ran into this issue. It means that that page is not editable in Gutenberg (vsb, visual site builder) In editor, below 'Edit with Oxygen' deselect the 'make page fully editable in Gutenberg' save, and it'll work.

DavidWooF commented 3 years ago

HI, @leeleevan I'm not sure if this problem persists after all updates but I remember that that was working even then but the edited version was the version after your first use of 'make page fully editable in Gutenberg'. So if I did as you say I did not have a user-modified version in the editor but the first version and if I edit that version all user edits were gone after save. I can't retest that now but will try in a couple of days when I find a time. And I also move from Polylang.

design1one1 commented 3 years ago

We really need that Also make css files work through id in the file name and not the slug

wpsumo commented 3 years ago

Same on WPML and once you create Gutenberg blocks. It fetches the data even if the data in the Gutenberg block is dynamic from the default language.

fifle commented 3 years ago

+1. This issue is already blocking our work for multilanguage sites for a long time. We really need to have some solutions for our customers to make their changes in more convinient way. Soflyy, please take a look into that issue ASAP.

polydevuk commented 2 years ago

2 years and 3 months since this thread started and still no solution. It's almost 60 days since I purchased Oxygen so I will probably be requesting a refund as this won't-fix attitude from Oxygen is a show-stopper for me. I bought Oxygen Builder for work on a new multi-lingual site for a big client but unfortunately I left the translations until the end after I had already invested heavily in Oxygen Builder to setup the rest of the site. Not at all impressed, Oxygen.

ramajestudio commented 2 years ago

There is a workaround that has worked pretty well for me. All you need to do do is to use the Oxygen blocks functionality.

  1. Save each section of your secondary language(s) page(s) as template blocks in Oxygen editor
  2. Back in Gutenberg, Check « make the page editable in Gutenberg »
  3. Send the error block to trash.
  4. Rebuild your page in Gutenberg adding the above saved blocks.

Works like a charm… only downsides are the extra work for creating blocks and the extra steps needed to edit the design afterwards (need to open Oxygen editor for every block, rather than once for the full page).

hope that helps!

pixluser commented 2 years ago

If you don't set polylang to translate templates, you'll not have the problem I guess. My oxygen designs are multilingual using conditions... that's perfect.

knut-studio commented 2 years ago

I am experiencing the same bug with:

I am able to “make this full page editable in Gutenberg” for the main language pages, but not for the translations.

ramajestudio commented 2 years ago

I am experiencing the same bug with:

* Oxygen 3.9

* Oxygen Gutenberg Integration 1.4

* Polylang 3.2.2

I am able to “make this full page editable in Gutenberg” for the main language pages, but not for the translations.

Use the block library as I explained above and your problem will be solved!

knut-studio commented 2 years ago

I am experiencing the same bug with:

* Oxygen 3.9

* Oxygen Gutenberg Integration 1.4

* Polylang 3.2.2

I am able to “make this full page editable in Gutenberg” for the main language pages, but not for the translations.

Use the block library as I explained above and your problem will be solved!

Thanks @ramajestudio! That's not an option for me, as I have a huge amount of pages translated. I would prefer to deactivate the Gutenberg integration and let my client edit the page texts via the Oxygen Builder, although it's not ideal. Thank you, anyway, for your help! 👍

loiceoka commented 1 year ago

This actually works! Translate templates need to be checked! Thank you for this tip!

supersuryaansh commented 10 months ago

Still an issue, lost many pages due to this.

philthebass commented 5 months ago

Is there anything new with this Polylang issue? I'm having exactly the same problem translating Oxygen pages that use the Gutenberg editor even with Translate Templates enabled. Thanks

supersuryaansh commented 5 months ago

@philthebass Oxygen + multiple languages is a nightmare, I am still facing this issue. My advice is that don't use Oxygen with multiple languages if you can.

philthebass commented 5 months ago

@philthebass Oxygen + multiple languages is a nightmare, I am still facing this issue. My advice is that don't use Oxygen with multiple languages if you can.

Thanks. Trouble is, we're well down the road with Oxygen now so it would mean a complete rebuild using an FSE block theme which we don't have the time or budget for

ramajestudio commented 5 months ago

Do not use the full page editing but use blocks created with Oxygen instead. You won't get any problem with Polylang anymore.

supersuryaansh commented 5 months ago

Saving every single element as Oxygen block is pain.

philthebass commented 5 months ago

Thanks @supersuryaansh - I fear you may be right sadly. Hindsight is a wonderful thing, but I wish we'd built an FSE Theme using something like Pinegrow

philthebass commented 5 months ago

Just an update on the work around we're using for now. As we're translating a site into 8 languages + English, we're reworking all of our static Oxygen pages to use ACF fields for all the content. It's a bit of a laborious task, but seems to work well and will cut down on the amount of time translators will need to spend on it as DeepL is taking care of the translations.