Block unsupported with Classic Editor

Hi @kybernetikservices,

It sounds like something went wrong during the conversion of the documents while switching between Gutenberg/Classic Editor.

While in the Classic Editor > “Text” mode, you can insert the documents using the document shortcodes as listed here: https://complianz.io/used-shortcodes-by-complianz/. This should make the documents appear properly when using the Classic Editor.

Example screenshot:

Hope it helps.
Kind regards,
Jarno

Thank you @jarnovos for your reply.
Unfortunately I didn’t explained the issue well.
With Classic Editor I have the option to choose whether I want to edit a post or page with the classic or block editor.

The page I mentiones (Cookie Policy) is in block editor mode. When I deactivate the plugin Classic Editor the block complianz/document shows the text as expected. When I activate the plugin the page is still in block editor mode but I get the message

Your site doesn’t include support for the “complianz/document” block. You can leave this block intact or remove it entirely.

So, the block is not available in block editor mode when the plugin Classic Editor is activated.
Could I explain the issue better?

@kybernetikservices this is the intended behaviour:
When Classic Editor is enabled, Complianz GDPR does not load the Complianz block. Otherwise resources are loaded unnecessarily. When using the plugin in Classic Editor, we recommend to use the classic shortcode.

Is there a use case which requires a Complianz Gutenberg block in combination with Classic Editor?

Thats what I wrote @rogierlankhorst. When activating the Classic Editor the “complianz/document” block is not supportet anymore.

The use case is, when I have a website created with the block editor but need some pages done with the classic editor. In this case I install the Classic Editor plugin and chooce block editor as the default editor. No change for the most pages and posts. Just the two/three pages which have to deliver content which is not possible to create with the block editor uses the classic editor.

I assume you expect when the Classic Editor is activated the user is using just the classic editor for each page and post. But this is not always the case. The classic editor allows the choice to use block or classic editor.
In my opinion it is not the best way to disable the “complianz/document” block when Classic Editor is activated. I would recommand to check also if the page is using classic or block editor and based on this you should enable or disable the block.

Just using the classic shortcode doesn’t work for you?

@rogierlankhorst The classic shortcode works for me. But, is not comfortable as the “complianz/document” block is ;-),

I understand if you won’t fix this. In this case I think you should show a message. Because in my case, I hadn’t a cookie policy text for over a month on my page. Because I didn’t check the cookie policy page after activating the classic editor.

Ok, thanks for your feedback. I will discuss this internally, and either clarify the behavior or enable the block in such cases.