Skip to content
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

Closed
ClassicRKR27 opened this issue Apr 14, 2023 · 7 comments
Closed

Navigation Block: Classic Menu not updating #75800

ClassicRKR27 opened this issue Apr 14, 2023 · 7 comments
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Menus Navigation [Pri] Normal Schedule for the next available opportuinity. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@ClassicRKR27
Copy link

ClassicRKR27 commented Apr 14, 2023

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

  1. Select the Blockbase theme
  2. Under Appearance > Menus create a menu
  3. Go to the Site Editor and create a Navigation block and select the Classic menu that you created in step 2
  4. If you try to make updates, you will not see them reflected on the live site

What 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

@ClassicRKR27 ClassicRKR27 added [Type] Bug When a feature is broken and / or not performing as intended User Report labels Apr 14, 2023
@github-actions github-actions bot added the [Pri] Normal Schedule for the next available opportuinity. label Apr 14, 2023
@github-actions
Copy link

github-actions bot commented Apr 14, 2023

Support References

This comment is automatically generated. Please do not edit it.

  • 6116791-zen
  • 6307953-zen

@ClassicRKR27
Copy link
Author

Another report here: 38618924-hc

@cuemarie
Copy link

cuemarie commented Apr 18, 2023

📌 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

@cuemarie
Copy link

cuemarie commented Apr 18, 2023

📌 SCRUBBING NOTES - CONTINUED

Atomic Test Site - Did Not Replicate issue as described

  • With Classic Theme Twenty Twenty activated, I used Appearance > Menus to create a menu called Classic Menu AT Site set to the site's "Desktop Horizontal Menu" location and saved
  • I then used Appearance > Customize to create another menu called Classic Menu AT Customizer with the same pages, but not assigned to any location.
  • Then switched to Theme Blockbase
  • Opened Site Editor and replaced default menu with my Classic Menu AT Site menu and saved
  • I returned to the site editor and made changes to the home template and the navigation block, saved, and viewed the site again. My changes appear, but the actual menu items are still incorrect.
  • However, once I edit the imported classic menu, the updated menu then appears. Here's an example of that using my other imported classic menu:
Screen.Capture.on.2023-04-18.at.13-35-06.mp4

This 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.

@cuemarie
Copy link

cuemarie commented Apr 18, 2023

📌 SCRUBBING : RESULT - Replicated / Could Not Replicate / Uncertain

📌 ACTIONS

  • Assigned to Cylon

📌 Message to Author

  • .@ClassicRKR27 - can you review the steps I've noted above and let me know if there are discrepancies between what I've tested and what you've tested? FSE and classic menus can get confusing, so I don't want to add to the confusion ☺️
  • Can you check to see if rearranging menu items allows the imported classic menu to appear on the live site as well?

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!

@cuemarie cuemarie added Menus [Status] Needs Author Reply Navigation [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. labels Apr 18, 2023
@cuemarie cuemarie added Triaged To be used when issues have been triaged. and removed [Status] Needs Author Reply labels Apr 18, 2023
@eduardozulian
Copy link
Member

Got one report in 6307953-zen. Rearranging a single menu item was enough to display the menu in the site's front end.

@annezazu
Copy link

annezazu commented Sep 9, 2024

Closing this out as the related Gutenberg issue was resolved previously! WordPress/gutenberg#49718

@annezazu annezazu closed this as completed Sep 9, 2024
@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Menus Navigation [Pri] Normal Schedule for the next available opportuinity. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

No branches or pull requests

4 participants