WordPress.org

Make WordPress Core

Opened 2 months ago

Last modified 4 days ago

#52790 reopened defect (bug)

Reusable blocks disappeared

Reported by: jordiparera Owned by:
Milestone: 5.7.2 Priority: normal
Severity: critical Version: 5.7
Component: Editor Keywords: reporter-feedback
Focuses: Cc:

Description

Hi,

After the 5.7 updated, my reusable blocks stopped showing on all the posts. Also, when I try to edit them again, it is impossible. I have (had) two reusable blocks: one for all my social icons and another one with a shortcode. Both are missing now.

Is there a possibility to restore the reusable blocks from my last backup? Unfortunately, I did not export them to a JSON file.

Thanks.

Attachments (3)

Bildschirmfoto 2021-03-12 um 18.09.09.png (195.1 KB) - added by mansoor1 2 months ago.
Broken Reusable Block Listed
Bildschirmfoto 2021-03-12 um 18.10.22.png (153.8 KB) - added by mansoor1 2 months ago.
Broken Reusable Block Editorview is empty
double-image-block-2.json (78 bytes) - added by mansoor1 2 months ago.
JSON File of the broken Reuseble Block

Download all attachments as: .zip

Change History (43)

#1 @desrosj
2 months ago

  • Component changed from General to Editor
  • Keywords reporter-feedback added

Hi @jordiparera,

Welcome to Trac! I'm sorry you are experiencing an issue with 5.7 on your site. Let's see if we can figure out what's going on.

When you say they are missing, can you explain where you have looked and where you expect them to be?

Also, can you elaborate a bit on what happens when you try to edit them? Also, can you head to site.com/wp-admin/edit.php?post_type=wp_block and see if your reusable blocks are listed there?

#2 @mansoor1
2 months ago

Hi,

My colleague have also the same Bug. But i cant reproduce it. Will give you also Feedback, if i found out HowTo Reproduce it.

#3 @mansoor1
2 months ago

I looked also under site.com/wp-admin/edit.php?post_type=wp_block and there is the reusable blocks and if i click on edit, then its empty. i also duplicate this reusable blocks, but the duplication is also empty like the json file.

@mansoor1
2 months ago

Broken Reusable Block Listed

@mansoor1
2 months ago

Broken Reusable Block Editorview is empty

#4 @mansoor1
2 months ago

The Problem is, that the Content of the Reusable Block get removed. And not the Reusable Block it self. See my attached screenshots

Broken Reusable Block Listed
Broken Reusable Block Listed

Broken Reusable Block Editorview is empty
Broken Reusable Block Editorview is empty

Last edited 2 months ago by mansoor1 (previous) (diff)

#5 @mansoor1
2 months ago

  • Severity changed from normal to critical

@mansoor1
2 months ago

JSON File of the broken Reuseble Block

#6 @desrosj
2 months ago

  • Keywords needs-testing needs-patch added; reporter-feedback removed
  • Milestone changed from Awaiting Review to 5.7.1

Thank you both for the additional information! I've moved this to the 5.7.1 milestone so it can be investigated further.

#7 @hellofromTonya
2 months ago

  • Keywords reporter-feedback added; needs-testing needs-patch removed

Hello @mansoor1 and @jordiparera ,

Thank you for the information and screenshots.

I'm not (yet) able to reproduce the problem when updating from 5.6.2 to 5.7 (tried in Chrome, Safari, and Firefox). Need a little more information to help to reproduce and further investigate:

Are you able to disable all of the plugins and switch to a default theme such as Twenty Twenty-One (not a child theme)? If yes, please go ahead and then recheck. Is the reusable block content is restored?

If yes:

  • It's likely a plugin or theme conflict. To identify which one, re-active one plugin at a time and recheck the reusable block. When it breaks again, note which one caused it.

If no:

  • What version of WordPress did you update from?
  • What browser are you using?

#8 @mansoor1
2 months ago

Hi @hellofromTonya,

Its a 3 weeks old fresh installed WordPress Version 5.6.2 with the freeversion of the Theme Astra Version 3.1.2 (https://wordpress.org/themes/astra/) and these Plugins are installed:

I did the Update with the Browser Google Chrome Version 89.0.4389.82 running on my Apple Macbook Pro 16 macOS BigSur Version 11.2.3.

I also revert the update via Serverautobackupsystem.
But all 3 times after Update to Version 5.7 i got the Issue with the broken Reusable Blocks.

Server

Server architecture	Linux 2.6.32-openvz-042stab145.3-amd64 x86_64
Web server	nginx/1.19.6
PHP version	7.4.15 (Supports 64bit values)
PHP SAPI	fpm-fcgi
PHP max input variables	10000
PHP time limit	1200
PHP memory limit	-1
Max input time	1200
Upload max filesize	512M
PHP post max size	512M
cURL version	7.52.1 OpenSSL/1.0.2u
Is SUHOSIN installed?	No
Is the Imagick library available?	Yes
Are pretty permalinks supported?	Yes
.htaccess rules	Your .htaccess file contains only core WordPress features.

Filesystem Permissions

The main WordPress directory	Writable
The wp-content directory	Writable
The uploads directory	Writable
The plugins directory	Writable
The themes directory	Writable

Media Handling

Active editor	WP_Image_Editor_Imagick
ImageMagick version number	1800
ImageMagick version string	ImageMagick 7.0.8-66 Q16 x86_64 2019-09-23 https://imagemagick.org
File uploads	Enabled
Max size of post data allowed	512M
Max size of an uploaded file	512M
Max effective file size	512 MB
Max number of files allowed	20
Imagick Resource Limits	
area: 128 GB
disk: 9.2233720368548E+18
file: 768
map: 128 GB
memory: 64 GB
thread: 1
GD version	bundled (2.1.0 compatible)
Ghostscript version	9.26

NGINX vHost Config

server {
        listen 52.140.164.76:80;

        listen 52.140.164.76:443 ssl http2;
		ssl_protocols TLSv1.2;
        ssl_certificate /var/www/clients/client32/web248/ssl/mydomain.com.crt;
        ssl_certificate_key /var/www/clients/client32/web248/ssl/mydomain.com.key;

        server_name mydomain.com *.mydomain.com;

        root   /var/www/mydomain.com/web/current;

        location ~ /\.well-known/acme-challenge/ {
	   root /usr/local/ispconfig/interface/acme/;
	   index index.html index.htm;
	   try_files $uri =404;
        }
if ($uri ~ /\.well-known/acme-challenge/) {
	   break;
}

        if ($scheme != "https") {
            rewrite ^ https://$http_host$request_uri? permanent;
        }


        index index.html index.htm index.php index.cgi index.pl index.xhtml;





        error_page 400 /error/400.html;
        error_page 401 /error/401.html;
        error_page 403 /error/403.html;
        error_page 404 /error/404.html;
        error_page 405 /error/405.html;
        error_page 500 /error/500.html;
        error_page 502 /error/502.html;
        error_page 503 /error/503.html;
        recursive_error_pages on;
        location = /error/400.html {

            internal;
        }
        location = /error/401.html {

            internal;
        }
        location = /error/403.html {

            internal;
        }
        location = /error/404.html {

            internal;
        }
        location = /error/405.html {

            internal;
        }
        location = /error/500.html {

            internal;
        }
        location = /error/502.html {

            internal;
        }
        location = /error/503.html {

            internal;
        }




        error_log /var/log/ispconfig/httpd/mydomain.com/error.log;
        access_log /var/log/ispconfig/httpd/mydomain.com/access.log combined;

        location ~ /\.(?!well-known/) {
            deny all;
            access_log off;
            log_not_found off;
        }

        location = /favicon.ico {
            log_not_found off;
            access_log off;
        }

        location = /robots.txt {
            allow all;
            log_not_found off;
            access_log off;
        }



        location ~ \.php$ {
            try_files /55bf8b1d1b1eff10621d62434c66f75d.htm @php;
        }

        location @php {
            try_files $uri =404;
            include /etc/nginx/fastcgi_params;
            fastcgi_pass unix:/var/lib/php5-fpm/web248.sock;
            fastcgi_index index.php;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            fastcgi_intercept_errors on;
        }






        brotli_comp_level 9;

        location / {
            client_max_body_size 100M;

            add_header Referrer-Policy origin always;
            add_header X-Content-Type-Options "nosniff" always;
            add_header X-XSS-Protection "1; mode=block" always;


            rewrite /wp-admin$ $scheme://$host$uri/ permanent;

            location ~*  \.(jpg|jpeg|png) {
                if ($http_accept !~* "webp") {
                    break;
               }
               try_files /imageconverter.php?path=$request_uri /imageconverter.php?path=$request_uri&optimize=true;
            }

            location ~*  \.(jpg|jpeg|png|gif|css|js|svg|ico|webp|eot|otf|woff|woff2|ttf)$ {
                expires 30d;
                log_not_found off;
            }

            location ~ js/container_.*_preview\.js$ {
                expires off;
                add_header Cache-Control 'private, no-cache, no-store';
            }

            error_page 418 = @cachemiss;
            if ($request_method = POST) {
                return 418;
            }
            if ($query_string != "") {
                return 418;
            }
            if ($http_cookie ~* "wordpress_logged_in_") {
                return 418;
            }
            if ($http_cookie ~* "comment_author_") {
                return 418;
            }
            if ($http_cookie ~* "wp_postpass_") {
                return 418;
            }

            try_files  /wp-content/cache/wp-rocket/$http_host/${request_uri}index-https.html =418;

            add_header "FP-Cache" "HIT";
            expires 7d;
            add_header "Cache-Control" "max-age=10, must-revalidate";

            location ~ \.php$ {
                try_files  /wp-content/cache/wp-rocket/$http_host/${request_uri}index-https.php  /wp-content/cache/wp-rocket/$http_host/${request_uri}/index-https.php $uri $uri/;

                include /etc/nginx/fastcgi_params;

                fastcgi_pass unix:/var/lib/php5-fpm/web248.sock;
                fastcgi_index index.php;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_intercept_errors off;

                fastcgi_temp_file_write_size 10m;
                fastcgi_busy_buffers_size    512k;
                fastcgi_buffer_size          512k;
                fastcgi_buffers           16 512k;
                fastcgi_read_timeout 1200;

                add_header "FP-Cache" "MISS";
                add_header "Cache-Control" "no-store, no-cache, must-revalidate, max-age=0";
                add_header "Pragma" "no-cache";

                    }
        }

        location @cachemiss {
            try_files $uri $uri/ /index.php$is_args$args;
        }





}

UPDATE: I think i found it. The Issue comes because of the outdated Plugin https://wordpress.org/plugins/duplicate-page/ which i replaced with the better plugin which is already up to date https://wordpress.org/plugins/wp-duplicate-page/ . And now i can't reproduce above Issue. If i will get the same issue in different WordPress Installation, then i will let you know. Thanks a lot for Feedbacks!

Last edited 8 weeks ago by mansoor1 (previous) (diff)

#9 @mansoor1
8 weeks ago

  • Resolution set to worksforme
  • Status changed from new to closed

#10 @hellofromTonya
8 weeks ago

  • Milestone 5.7.1 deleted

#11 follow-up: @mansoor1
8 weeks ago

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Issue is still there. Today my colleagues tested it on different WordPress Sites and it comes again :-(. So the above Solution didnt work.

#12 @davelo
8 weeks ago

I got the same kind of issue, even more critical.
Everywhere the block was used, the front of the page went black, a critical error.

In the admin, on that block i got the error: Block cannot be rendered inside itself.

On the admin page of all the reusable blocks, i noticed that specific block was empty, as described in this ticket.

#13 @mansoor1
8 weeks ago

  • Severity changed from critical to blocker

#14 in reply to: ↑ 11 @hellofromTonya
8 weeks ago

Replying to mansoor1:

Issue is still there. Today my colleagues tested it on different WordPress Sites and it comes again :-(. So the above Solution didnt work.

@mansoor1 for your colleague, were any plugins activated? If yes, what happens when all of the plugins are deactivated?

Why? Trying to isolate if the problem is coming from WordPress Core or one or more plugin(s).

This ticket was mentioned in Slack in #core-editor by hellofromtonya. View the logs.


8 weeks ago

#16 @hellofromTonya
8 weeks ago

  • Milestone set to 5.7.1

Moving it back into the milestone for further investigation, pending reporter feedback.

#17 @davelo
8 weeks ago

Hi, don't know how to communicate in trac.
But i though it would be okay to record a screencast, as i'm really worried about the new workflow of Resuable blocks in 5.7. We need to address that, now it's just creates doubts and bloated blocks for the user.

Screencast: https://share.woofers.be/mXu1eo8o

#18 @hellofromTonya
8 weeks ago

@davelo thank you for your report and sharing the screencast. The UI and workflow pain points you identify are different than the issue reported in this ticket. To ensure these are not lost in this ticket, can you open a new Trac ticket by going here? Instructions on how to report are https://make.wordpress.org/core/handbook/testing/reporting-bugs/#reporting-a-bug.

#19 follow-up: @davelo
7 weeks ago

Hi, is there any news of feedback around this ticket?
We have immensive problems with disappearing reusable blocks.
The workflow around reusable blocks since 5.7 is really become very unpleasant.

Now, i noticed the following:

  • i remove a reusable block from a page
  • i come back to the page, do some edits; saves it and the page "asks' if i want to save the resuable block; yes; that same resuable block which was removed before.
  • looking in the code editor; i see some leftovers like this: <!-- wp:block {"ref":20341} /--> i found that code at the bottom of the page; which was not in the place where the reusable block was placed originally.

And i think this is the big issue.
Because of the "leftover"-reusable code-tags; the reusable blocks are getting overwritten with ... nothing. In other word: the reusable block is gone; and there are no revisions; and a backup doesn't solve the issues, i just creates a loop for the issue to come back.

A critical issue, i believe.

#20 in reply to: ↑ 19 @hellofromTonya
7 weeks ago

Replying to davelo:

Hi, is there any news of feedback around this ticket?

Current status:

  • Unable to reproduce the problem
  • Awaiting feedback if the problem persists after disabling all plugins and using a default theme

Replying to davelo:

We have immensive problems with disappearing reusable blocks.

Can you share more context and the steps to reproduce "disappearing reusable blocks"? Are you having the same issue reported in this ticket of reusable blocks no longer showing on the posts and not editable after upgrading to 5.7?

Reading your 2 comments, I think (please correct me if I'm wrong) you're having (a) a different issue and (b) want to report a workflow problem. Is this correct?

  • If yes, please open a new ticket for each to ensure each gets its own consideration and investigation. Else, these can get lost in this ticket as it's focused on a different issue.
  • Also, try disabling all plugins and using a default theme such as Twenty Twenty-One. Do the problems persist? Why? By disabling the plugins and using a default theme, it can help to isolate if the problem is coming from WordPress Core or elsewhere. Please note, there are reports of plugin conflicts causing issues with reusable blocks.

#21 @hellofromTonya
7 weeks ago

Possibly related Gutenberg issue (was due to a plugin conflict) - linking to group all reports of Reusable Blocks issues

#22 @hellofromTonya
7 weeks ago

Possibly related Gutenberg issue - linking to group reports of Reusable Blocks issues

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


6 weeks ago

#24 @audrasjb
6 weeks ago

Hello, I tried to reproduce the issue on my side, but it works well. On a fresh install, and also on some other existing WP installations.

#25 @jordiparera
6 weeks ago

The problem persists even after deactivating all the plugins.

This is a critical and urgent issue.

I suggest leaving the reusable blocks just the way they were before the latest involved updates.

Thanks.

#26 @audrasjb
6 weeks ago

Hello @jordiparera, can you please provide detailed steps to reproduce the issue on a WordPress fresh install?

#27 @jordiparera
6 weeks ago

Hello,
As commented to old reusable blocks disappeared from all the pages where they've been so far.

The fact is that the new created reusable blocks do work (so far), so for a new install, if you create new R.Bs I guess they will be fine.

But the OLD ones are not shown in the post they were attached, and when you edit the old posts the R.B. appear just empty and when you try to edit it, it responds "Block cannot be rendered inside itself."

Sorry, I don't know how can I add an image to this form.

This ticket was mentioned in Slack in #design by joyously. View the logs.


5 weeks ago

This ticket was mentioned in Slack in #design by jameskoster. View the logs.


5 weeks ago

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


5 weeks ago

#31 @audrasjb
5 weeks ago

Moving to Milestone 5.7.2 as WordPress 5.7.1 Release Candidate 1 is planned for today.

#32 @audrasjb
5 weeks ago

  • Milestone changed from 5.7.1 to 5.7.2

#33 @edragonxx
2 weeks ago

Same here, updated wordpress and voila reusable blocks are useless now!!!

How to reproduce that bug? Simple, make a reusable block, now add it to your posts. Next time add it to new post, press "covert regular block" because sometimes you just want use it as template, like have block styles and stuff put in place but you want change text there, so you will use reusable blocks convert them to regular block and author was able to add their own text without changing text every other post too, worked perfectly. Not anymore, once you press convert regular block it will empty reusable block. Every fucking single time!

#34 @audrasjb
2 weeks ago

@edragonxx I tried to follow the steps you described in your comment and I'm not able to reproduce the issue on a fresh install.

Here is a video of the steps I followed: https://i.gyazo.com/7ea9ae3696ad89550a051fcb563865aa.mp4

Could you please provide more details about the issue? Does it occurs with both existing and new reusable blocks? Are you creating the reusable blocks on the same page you're converting them to regular ones? Any detail may help to reproduce the issue.

ps: please watch your language, the last sentence of your comment is not appropriate. Thank you :)

#35 @jagenda
2 weeks ago

Not sure if this is related but I've noticed a couple of changes that allow users to accidentally break their Reusable Blocks.

The block validation now strips content from Reusable Blocks that have other Reusable Blocks inside them. This is fine, but I find it odd that you're still allowed to add those nested blocks instead of preventing users from doing so in the first place.

Not only that but previously Reusable Blocks were not editable in the page editor, which meant that you were relatively safe from mistakes. What happens now though, is that the Add New Block (+) button inside Reusable Blocks is indistinguishable from the page content's Add New Block buttons and users keep adding nested Reusable Blocks by accident. The previous heading for Reusable Blocks is also missing, which would make it clearer, along with a clear outline, where a Reusable Block begins and where it ends.

My suggestion would be to disable the ability to add nested Reusable Blocks altogether, and to prevent Reusable Block edits inside pages. If not the latter then at least clarify which content belongs inside the Reusable Block and which is current page content. Adding a clear heading and border that does not require selecting the block and in fact makes it easier to click on.

Again, these may be separate issues but the outcome is definitely the same and has caused grief among clients who do not know how to check if a block is Reusable before adding more Reusable blocks into it. I understand there is a new Post Update system to select which content you want to save but it's been poorly documented (no mention of it anywhere in the patch notes) and this does not help less tech savvy end-users from adding content in the wrong place and having to fix it later, wasting valuable time.

#36 @travisburch
2 weeks ago

I'm having similar issues.

Reusable blocks have become unusable. Lose all integrity when edited/added/modified from a post.

Deleting themselves, lots of stuff. I've also had links delete themselves, and trouble Saving/Updating posts.

All of these issues are occurring even on fresh installs w/o any plugins.

Hosting techs (WPEngine) can't seem to replicate it -- though I'm seeing it on multiple (clean) browsers, and on multiple computers, on fresh WP installs.

Fwiw, I've never used the Autoptimize plugin.

Last edited 4 days ago by travisburch (previous) (diff)

#37 follow-up: @mrschaal
2 weeks ago

I've also been experiencing the same issues on WordPress 5.7.1 using the Virtue Premium Theme.

Additionally, adding new reusable blocks via clicking on "Add to reusable blocks" at the context menu of a block within the Gutenberg Editor while editing a page has not been working anymore either. It seemed that the click has been registered, but the block won't change at all and also has not been added to the list of reusable blocks.

By deactivating all plugins and re-activating them one by one again, I've found out that the plugin "Autooptimize" causes this issue. As soon as I have deactived it, the issues were gone!

Now I can at least create new blocks, but can't reference them within any other page than the page on which they have been created. The widget for adding reusable blocks won't find the newly created one. Therefore I have no chance to find and embed the reusable block while editing another page anymore.

This ticket was mentioned in Slack in #core-editor by vdwijngaert. View the logs.


13 days ago

#39 in reply to: ↑ 37 @OptimizingMatters
13 days ago

That's somewhat surprising, as Autoptimize does not optimize admin-pages @mrschaal ... That being said, have you tried reconfiguring AO (e.g. disabling JS optimization or other settings) to see what might be happening here?

Replying to mrschaal:

I've also been experiencing the same issues on WordPress 5.7.1 using the Virtue Premium Theme.

Additionally, adding new reusable blocks via clicking on "Add to reusable blocks" at the context menu of a block within the Gutenberg Editor while editing a page has not been working anymore either. It seemed that the click has been registered, but the block won't change at all and also has not been added to the list of reusable blocks.

By deactivating all plugins and re-activating them one by one again, I've found out that the plugin "Autooptimize" causes this issue. As soon as I have deactived it, the issues were gone!

Now I can at least create new blocks, but can't reference them within any other page than the page on which they have been created. The widget for adding reusable blocks won't find the newly created one. Therefore I have no chance to find and embed the reusable block while editing another page anymore.

#40 @emilymoran84
9 days ago

  • Severity changed from blocker to critical

I hope this is the appropriate place to add this. (I'm not entirely versed in how core trac works, so please let me know if I should be starting a new ticket or placing this elsewhere). I just wanted to add that I've also found my reusable blocks are no longer in the "directory" if trying to add a new block. (I used to be able to search by the reusable block names). And I'm unable to make new ones. Here is a breakdown of what I'm seeing:

On the Reusable Blocks "List" page (/wp-admin/edit.php?post_type=wp_block)

  • My reusable blocks are still showing in the "list" page (/wp-admin/edit.php?post_type=wp_block), and I am able to go into their edit screen and see their content.
  • While I can access the "Edit" screen of a reusable block if going to the List of them, the "Update" button results in no action, thus making it impossible to actually edit existing blocks.
  • While I can click the "Add New" button on the list page (new block edit screen opens to /wp-admin/post-new.php?post_type=wp_block), when clicking "publish", it does the publish confirmation ask, then I click "Publish" again and it goes back to the first "Publish" button, never actually allowing me to publish the block

Within a post or page

  • Reusable blocks do not come up in the block search and there is no "Reusable" tab in the block sidebar (Should be "Blocks" "Patterns" "Reusable") Screenshot: http://snpy.in/RMQBcp
  • Existing reusable blocks already within content still seem to be displaying the reusable block's content and have something of a "ghost frame" of what should be the frame for editing them within the post they're embedded within, however the option is not present. Screenshot: http://snpy.in/H1JtpQ
  • If I switch to code editor view, I can see the HTML for the block, and it seems (at least from one test), that I can add an existing reusable block to a post if I flip to the Code Editor view and paste in the HTML (though cannot make new reusables). Example of the HTML:
<!-- wp:block {"ref":20311} /-->
  • I am unable to save new reusable blocks from within a post or page. Clicking the "Add to Reusable blocks" results in nothing happening.

Note: While I do have the Autoptimize plugin, it is not active (I saw that for another poster, disabling that plugin fixed some issues).

. Thank you!

Last edited 9 days ago by emilymoran84 (previous) (diff)
Note: See TracTickets for help on using tickets.