-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation Block: Classic Menu not updating #75800
Comments
Support References This comment is automatically generated. Please do not edit it.
|
Another report here: 38618924-hc |
📌 SCRUBBING NOTES While trying to replicate, I ran into a couple variations on what you've reported, so I wanted to break those steps out here, in case they lead us down different paths. Simple Site Test - Did Not Replicate issue as described
|
📌 SCRUBBING NOTES - CONTINUED Atomic Test Site - Did Not Replicate issue as described
Screen.Capture.on.2023-04-18.at.13-35-06.mp4This matches the behavior I saw in the simple site test as well - rearranging menu items (or likely other menu item changes, but not styles changes to the nav block) is needed to have the live site reflect the correct menu. |
📌 SCRUBBING : RESULT - Replicated / Could Not Replicate / Uncertain
📌 ACTIONS
📌 Message to Author
Since I was able to replicate this behavior pretty consistently in Dotcom and self-hosted, I think we have enough to bring this to Cylon. But it'd be great to confirm if my tests match your experience, and perhaps we can update the original report a little to reflect those findings. Thanks! |
Got one report in 6307953-zen. Rearranging a single menu item was enough to display the menu in the site's front end. |
Closing this out as the related Gutenberg issue was resolved previously! WordPress/gutenberg#49718 |
2023-04-18 update - I actually think this is impacting all themes, not just Universal/Blockbase; and a workaround is to rearrange the items in the imported menu in the editor - that seems to force the menu to update on the live site as well. -cuemarie
Quick summary
This is related to this open core report, but it was suggested that I make a report for Calypso as well.
Essentially, on Universal/Blockbase themes we're still seeing an issue where selecting a
Classic
menu is able to be selected but when changes are made they do not reflect on the live site. This was reported here though I have seen this crop up before. I haven't been able to find any other open reports of this, but essentially this is forcing users to have to recreate their menus completely from scratch.Steps to reproduce
Classic menu
that you created in step 2What you expected to happen
The Classic Menu edits should be showing on the live site.
What actually happened
The menu remains unchanged on the live site.
Impact
Most (> 50%)
Available workarounds?
Yes, easy to implement
Platform (Simple and/or Atomic)
No response
Logs or notes
No response
The text was updated successfully, but these errors were encountered: