Opened 3 months ago
Closed 2 months ago
#65917 closed defect (bug) (invalid)
ACF Block Layout Changed After Update WordPress 7.1
| Reported by: | jenish1234 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Editor | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: | ui |
Description (last modified by )
I am facing a difference in the ACF Custom Gutenberg Block editor layout between WordPress version.
After Update WordPress 7.1, When I add a ACF Block, the block editor layout appears like Attached Before Image.
In the older WordPress version(<7.1) The ACF Block appears like the After image, which is the layout User expect and prefer.
I am using the same Advanced Custom Fields PRO version 6.8.7.
Is the change in the ACF block layout caused by a UI change in the Gutenberg/WordPress block editor in WordPress 7.1, or is there a setting or configuration I need to adjust to restore the second layout?
It looked good before, but now it looks really weird because when ACF opens the repeater field, it looks really awkward for the user.
Attachments (4)
Change History (16)
#1
@
3 months ago
- Description modified (diff)
- Summary ACF Block Layout Changed After Update WordPress 7.1 Update → ACF Block Layout Changed After Update WordPress 7.1
#3
@
3 months ago
@jenish1234 Is the block that you are creating using block version 2 or block version 3? If it is using block version 2, it needs to be updated.
#4
@
3 months ago
Hi @jorbin,
Thank you for your response.
I checked my ACF block registration and confirmed that the block is currently using Block API version 2.
Could you please clarify what changes are required to update an ACF block from Block API version 2 to version 3? Specifically, I would like to understand whether updating to Block API version 3 would restore the previous editor layout.
I am currently using ACF PRO 6.8.7, and the same block worked as expected in WordPress versions prior to 7.1.
The issue started after updating to WordPress 7.1.
There are no issues with version 7.0.4 you can use it without any problems.
Are there any known changes in the WordPress 7.1 block editor layout or behavior that could affect how ACF blocks are displayed in the editor?
Thank you!
#5
@
3 months ago
Could you please clarify what changes are required to update an ACF block from Block API version 2 to version 3?
I was able to find https://www.advancedcustomfields.com/resources/acf-blocks-v3/#upgrading-to-v3 which includes some instructions.
#6
@
3 months ago
- Resolution → fixed
- Status new → closed
Thanks for the reference, @jorbin.
Since this ticket is related to ACF, I'll proceed with closing it.
#7
@
3 months ago
- Resolution fixed
- Status closed → reopened
Hello @jorbin ,
I have checked the link you shared and also tested both ACF Block Version 2 and Version 3. However, the ACF layout is still broken and remains the same in both versions.
I'm still facing the same issue. Could you please advise if there are any additional changes or settings required to fix the layout?
#8
@
3 months ago
Hey @jenish1234,
Just to clarify, you'll want to make sure that both core's blocks version and ACF blocks version are both set to 3.
Here's a stripped down block.json to demonstrate:
{
"$schema": "https://schemas.wp.org/trunk/block.json",
"apiVersion": 3,
"acf": {
"blockVersion": 3
}
}
#9
@
3 months ago
Hello @jorbin
We are not using block.json in our implementation. Instead, we are creating custom ACF blocks and adding, so there is no block.json file involved.
#10
@
3 months ago
Hi, Iain Poulson from the ACF team here.
To clarify: ACF Blocks V2 using Edit mode is not compatible with the iframed editor in WordPress 7.1. This is expected behavior, not a regression we can address from ACF. The WordPress 7.1 iframe change means the wp-admin scripts that powered V2 Edit mode are no longer available inside the editor canvas.
ACF Blocks V3 is the supported path for WordPress 7.1 and later. We have published a full explanation of the change and migration guidance here: https://www.advancedcustomfields.com/blog/acf-6-8-9-released/
If you have migrated to V3 and are still experiencing issues, we would want to investigate that. Please open a GitHub issue with steps to reproduce and we will look into it: https://github.com/AdvancedCustomFields/acf/issues
For teams that need more time to migrate, we have also published an official compatibility plugin that temporarily restores V2 behavior: https://github.com/AdvancedCustomFields/acf-blocks-v2-iframe-compatibility
#11
@
2 months ago
Hi @polevaultweb
I`m currently using WordPress 7.1 version with Advanced Custom Fields PRO 6.8.8 version.
As suggested, I installed and activated the "ACF Blocks V2 Iframe" capable plugin from the GitHub repository and tested it with my existing ACF Blocks V2 setup.
After following your recommended approach, the blocks are now working properly in the WordPress 7.1 editor, and the issue I was facing has been resolved.
Thank you for the guidance and for providing the compatibility plugin. As per your instructions, I followed the steps, and everything is now working properly as expected.
#12
@
2 months ago
- Milestone Awaiting Review
- Resolution → invalid
- Status reopened → closed
- Version 7.1
Great to hear this is resolved! Thank you @polevaultweb and @johnstonphilip for jumping in to help!
I've closed this ticket of with the term invalid, in this case it's the unfriendly term trac uses to indicate that there wasn't a core issue at root, not that the issue wasn't valid for the specific implementation.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
in 7.0.4 Version(Before)