gildner

I like to add a few things here: We also use this plugin on multiple sites and were happy with it. Meanwhile we could get this error multiple times more often. We were able to reproduce this error fairly often by using two different users.

1. On multisites when one super-admin user creates the block, it is fine. When a normal admin is opening the site/post afterwards the block is broken. We used two different browsers to test this.
2. On normal sites we have this error coming more irregular, but more often. When using two users with different/multiple roles

Since this plugin isn’t reliabel anymore, we will remove it from our websites and probably stop using it.

Hi,

thanks for your reply. The issue occurs on sites where the block is used.

The “style” panel on the right side of the editor. The regular image “style” is blocked by a after-element with content “pro”.

You can see this on the screenshot below.

I looked via the inspector and found that the after element on the “style” panel is “aab-” wich seems to be your commonly used prefix.

I can provide screenshots if needed

• This reply was modified 8 months, 4 weeks ago by gildner.

I did some experiments meanwhile.

The problem has something todo with how the blocks are rendered. Even when using the_content() (e. g. when creating a archive.php), then the blocks won’t render as they would do normally.

Here the code I used.

<?php get_header();

global $post;

$page_id = get_queried_object_id();

$post = get_post($page_id, OBJECT);
setup_postdata($post);

the_content();

wp_reset_postdata();


get_footer();

Any idea on how to resolve this? Is there a possibilty to re-trigger the creation of inline-styles and scripts when using this?

I keep trying to find a solution for this.

Hi Andrei,

Thanks for responding!
I sent you a mail request yesterday ??

Great to hear and thanks for the quick response! ??