-
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
"WP Admin equivalents" setting not respected for widgets and menus #49830
Comments
@obenland I suggest that "Widgets" & "Menus" load the WP Admin screen and not the customizer when "Replace all dashboard pages with WP Admin equivalents when possible" is enabled for Atomic sites only. Especially customers who use WPML will need |
I'm curious, why only on Atomic sites? That doesn't seem to be respecting the current wording of the setting. |
That's a good point @kriskarkoski, thanks for raising it. I suggest doing so only for Atomic cause we:
|
That's fine, let's also apply that to all environments. |
I'd not consider this launch blocking at this point |
Reopening this, as it appears nav links to WP Admin versions of the menu and widget pages are once again pointing to the Cusomizer for Atomic sites. Accessing the pages directly works as expected at User report: 4284607-zen. |
@inaikem I think that's the intended behavior. See p1628525963071300/1628262477.060300-slack-CB0B2G43X p1628193314037400/1628119959.008100-slack-C021Z8P3RMG. As of Automattic/jetpack#20587, all these menus point to the Customizer. |
Thanks Miguel! I am curious, though. I was under the impression that we would continue to point Atomic users to the WP Admin screen when they have the "Classic View" selected under screen options - I may well have made that up but would like to clarify all the same! |
Unfortunately, the layout of Customizer screens doesn't offer a screen options button, so we couldn't provide users the ability to choose their preferred view (see #55231). |
Agreed. I appreciate there's limited screen real estate in the Customizer to add a dedicated toggle and should have been clearer: I'm advocating that for Atomic sites, whenever the Classic view is active via the screen options panel (regardless of where it was selected), we should be redirecting clicks to |
Aren't "screen options" meant for setting showing Calypso/wp-admin views, whereas here we have just wp-admin views, and no Calypso views? |
That's right, I forgot that we link to the WP Admin Customizer, and thus only the classic view is supported by the screen options. In order to allow users to switch between Alternatively we can keep the default widgets menu registered by Core which links to |
Linked issue with user reports here: #55388 |
From interaction 18097743-hc ...now WordPress.com has updated to a new Menu creation/editing screen and the old is completely gone. All of the functionality that I relied upon is now completely gone as well. Why would the team get rid of a screen completely. I'd like access to the legacy menu building screen. |
Copying over the feedback I've shared on the respective issues related to the core Widgets and Menus navigation. This change has been generating numerous support interactions and HE reports. The workaround is to have the user remember or bookmark the direct link to the pages.
-- Having the option to navigate to the core WP-Admin pages is essential for WordPress.com on Atomic sites using third-party themes and plugins. If we keep this new behavior, there absolutely needs to be an option to toggle this off or have a workaround for WoA sites that need to use the WP core behavior. Why? Those pages are essential for numerous popular third-party plugins and themes. In some cases, the options are not available in the Customizer. -- Example • wp-admin/nav-menus.php Many sites using a plugin like Additionally, editing block widgets in the Customizer is a bit problematic in its current iteration. At times, it's much easier to navigate and edit in the dedicated WP-Admin page. -- Related internal discussion: p1631178748139800-slack-C7YPUHBB2 |
Closing this one out, since “Appearance > Widgets” and “Appearance > Menus” now link back to classic “widgets.php” and “nav-menus.php” destinations for Simple and Atomic sites! |
Steps to reproduce the behavior
What I expected to happen
Widgets and Menus to open their WP Admin equivalent
What actually happened
They opened in the Customizer
Does this happen on simple or atomic sites or both?
Both
Level of impact (Does it block purchases? Does it affect more than just one site?)
All sites, but low impact. The pages can still be accessed by direct URL
Screenshot / Video: If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: