Make WordPress Core

Opened 9 months ago

Closed 8 months ago

#61693 closed defect (bug) (reported-upstream)

New WP Core 6.6 prevents switching views in Gutenberg Page Builder

Reported by: amrartist2009's profile amrartist2009 Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.6
Component: Editor Keywords:
Focuses: ui, administration Cc:

Description

I've noticed that in multiple sites, the WP core update prevents the switching of views from desktop to tablet or mobile when using the Gutenberg builder - something that doesn't occur when using 6.5.5. I've had to rollback multiple sites so my clients can utilize the different views when building new pages.

Utilizing the Neve theme.

Change History (14)

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


9 months ago

#2 @hellofromTonya
9 months ago

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

Hello @amrartist2009,

Welcome to WordPress Core Trac. Thank you for reporting this issue.

Does "Gutenberg Page Builder" mean the Gutenberg plugin is activated on these sites? If yes, what's the plugin version?

Tentatively moving into 6.6.1 while assessing impact, given RC is planned for later today.

#3 @amrartist2009
9 months ago

Hey Tonya, No the plugin is not active, just utilizing the native Gutenburg builder that comes with WP Core.

#4 @hellofromTonya
9 months ago

  • Keywords reporter-feedback removed
  • Milestone changed from 6.6.1 to 6.6.2

Thank you for confirming @amrartist2009.

In talking with @ellatrix, curious if this is a known issue and has a bugfix going into 6.6.1.

If no, it'll also need to be reported upstream in Gutenberg (as the fix would happen there).

cc @ellatrix

With 6.6.1 RC happening within a few hours, moving this ticket to 6.6.2. But after RC is released, would be great to retest to see if the issue is fixed (can then be put back to 6.6.1 and closed).

#5 @ironprogrammer
9 months ago

@amrartist2009, is this the Neve you're referring to? Running that theme in Playground shows that it's got its own options panel for building post/page layouts that are controlled by the theme itself (this isn't an FSE theme).

Would you be able to provide some screenshots or a short video showing the issue you're seeing, and whether it occurs for any other theme(s)? Thanks!

#6 @amrartist2009
9 months ago

Yes that is the correct theme. It does allow custom post/page layouts but those work in the same way that archive.php or single.php would, giving you a place to build your content with dynamic inputs. The issue is happening simply by adding a page, and building that page with the Gutenberg builder.

It does seem to be working in the playground - so now I'm not sure if it's a conflict with something or the Pro version of the theme. Rolling back to 6.5.5 did fix the issue for me though.

Ok messed with plugins, the issue seems to be with Neve, Yoast SEO, and WP 6.6. If I roll it back to 6.5.5 it works. When Yoast is turned off on WP 6.6 it works.

I can reach out to the plugin and theme authors and see what they're doing to ensure compatibility with the latest core update.

#7 @ironprogrammer
9 months ago

Thanks for the additional context, @amrartist2009. Indeed, in Playground running 6.6 and Yoast SEO, the tablet/mobile views do not appear to work (compare to Playground running 6.5). This looks to be related to the display of the plugin's meta box, and IMHO should be considered a regression.

In a cursory search in Github issues, I couldn't find a ticket about this, and would encourage you to check and report upstream as recommended by Tonya if you also cannot find a similar bug (it's also possible Yoast is aware of this and may file an issue or have a workaround planned).

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


9 months ago

#9 @hellofromTonya
9 months ago

Discussed this ticket in today's bug scrub ahead of 6.6.2 RC1 (tentatively earmarked for the week of Aug 19th).

@vcanales is this one on your radar? Is it a known issue? If no, do you agree it should be reported upstream in the Gutenberg repo?

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


8 months ago

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


8 months ago

#12 @wildworks
8 months ago

This is a known issue and was reported here: https://github.com/WordPress/gutenberg/issues/63708
This issue has also been fixed and has been given a backport label: https://github.com/WordPress/gutenberg/pull/63724#issuecomment-2246838419

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


8 months ago

#14 @hellofromTonya
8 months ago

  • Milestone 6.6.2 deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

As mentioned, this issue is known and already fixed in Gutenberg. The fix will be included in the npm package updates for 6.6.2 RC1. Closing it as reported-upstream, since its investigation, resolution, and code is handled and maintained in the Gutenberg repository.

Note: See TracTickets for help on using tickets.