Support

Account

Register Login

Home › Forums › Backend Issues (wp-admin) › Blocks appearing in the sidebar after updating to WordPress 7.1

Solving

Blocks appearing in the sidebar after updating to WordPress 7.1

  • Do not update to 7.1 if you want to keep the blocks usable…
    They’re all appearing in the sidebar so the blocks become unreadable at width 280px. Issue was not present before updating to 7.1

    Screenshot-2....png

  • Same here, all my sites are broken in the back office and can no longer be edited (I hide the block panel on the right since it’s useless).

  • same here, wordpress is givin us nightmares for all the projects created with acf custom blocks.
    i downgraded to 7.0.4 and locked updates only to minor/security for the time being.

    hope someone comes up with a solution!

  • Yep – broken here too. Only solution at the moment is to roll back core.

  • Updating any custom blocks to ACF Blocks V3 does seem to be at least a partial solution, as it gives access to the ‘Extended Editor’ from the sidebar.

  • Thanks for the tip @krakow – updating all of my custom blocks to v3 brought the Edit button back and enabled the Extended Editor.

  • Same issue here, this is insane to not be able to edit the block in the same place where it stands the “preview” and go to the sidebar which is a small area.
    ACF team must come with a solution, otherwise for me is useless ACF, I will look for another plugin.

  • Or at least to be able to have the modal when we click over the preview area, not to go in the sidebar to click another button and the modal should be styled to stay in the middle of the page, something like a modal centered with 90vw width on a 90vh height.

    feedback.jpg.jpg

  • Upgrading to v3 ACF blocks semi-fixed it for me too, you now get the preview looking ok, and you can click the edit icon to pull out the sidebar so it is bigger.

    I still hate it though, I don’t want to preview my blocks, this is a backend editor, I want clean inputs so I can put in the data. This is trying to be a frontend editor, which I do not want!

  • ACF have published an article that explains the cause of the issue and migration options, including a v2 compatibility plugin.

    https://www.advancedcustomfields.com/blog/acf-6-8-9-released/

    For my purposes setting blocks to v3 and disabling inline render previewing is the cleanest migration path for blocks that previously had inline editing and no preview:

    “acf”: {
    “blockVersion”: 3,
    “renderPreview”: false,
    “renderTemplate”: “blah.php”
    },

  • this plugin https://github.com/mwpanerio/acf-force-edit-mode work and temporary solve the issue

  • Thanks for the continued discussion. A few things to add.


    @iskis    : for the compatibility plugin, we would point to our official one rather than a third-party: https://github.com/AdvancedCustomFields/acf-blocks-v2-iframe-compatibility. It is a temporary bridge while you plan migration, not a long-term fix, but it is the supported option.

    For those migrating to V3 and wanting to replicate the old “always in edit mode” experience, @jnicol is on the right track. You can go further with a couple of additional options:

    In block.json, adding “renderPreview”: false to the “acf” key shows a clean placeholder with an “Edit Block” button that opens the Expanded Editor, bypassing the preview entirely.

    You can also prevent fields from ever appearing in the narrow WP sidebar by setting “hideFieldsInSidebar”: true, so all editing happens in the Expanded Editor only.

    If you are registering via PHP rather than block.json, the equivalent options are render_preview and hide_fields_in_sidebar (underscores instead of camelCase).

    Full configuration options: https://www.advancedcustomfields.com/resources/acf-block-configuration-via-block-json/

    Full release post for 6.8.9: https://www.advancedcustomfields.com/blog/acf-6-8-9-released/

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.