Postponed
Project:
Drupal core
Version:
main
Component:
node system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Aug 2021 at 04:42 UTC
Updated:
20 Mar 2025 at 00:41 UTC
Jump to comment: Most recent
This issue has been created as a follow up for #3220437-36: [PP-1] Empty breadcrumb at node/add and node/add/{content_type} when frontpage view is enabled
In issue #3220437: [PP-1] Empty breadcrumb at node/add and node/add/{content_type} when frontpage view is enabled, we have added a Breadcrumb Builder service. This was designed to be only a backwards-compatibility layer.
Remove the backwards compatibility layer introduced in #3220437: [PP-1] Empty breadcrumb at node/add and node/add/{content_type} when frontpage view is enabled (including the Breadcrumb Builder), and move the node/add/{content type} paths to sit under admin/content.
admin/content;
Comments
Comment #2
mohit_aghera commentedComment #3
aaronmchaleUpdated IS to use proper issue links and added a bit of formatting.
Removed "Create redirects for older paths for backward compatibility." from proposed resolution steps as we are removing the BC-layer in this issue.
Moved Proposed Resolution steps to sit under Remaining Tasks.
Refactored Problem and Proposed Resolution sections, we don't need a "Steps to reproduce" section.
Comment #4
aaronmchaleObviously this is blocked on #3220437: [PP-1] Empty breadcrumb at node/add and node/add/{content_type} when frontpage view is enabled.
Comment #5
alexpottMoving the node/add pages under admin/ is really quite a big change that needs quite a lot more work than is suggested in the issue summary, There is a toggle to display node creation pages in the frontend theme i.e. not the admin theme. This will break the moment we move the node creation paths. At the moment \Drupal\node\EventSubscriber\NodeAdminRouteSubscriber takes care of marking these non-admin paths as admin paths if the node_settings::use_admin_theme config is set to TRUE. All of this will need much thought. Also the entire use case of user generated content will be affected.
Comment #6
aaronmchale@alexpott Great points there, thanks. I've added "Figure out how to handle the existing "Use admin theme" config option" as a remaining task.
Yeah that's a really important point, and definitely worth exploring. Definitely implications for #3220437: [PP-1] Empty breadcrumb at node/add and node/add/{content_type} when frontpage view is enabled (which we're already discussing over there).
One example of that user generated content, off the top of my head, would be for a site using the Forum module, when creating a new topic, for end users you would want them to stay in the context of the site frontend and not take them out of that experience into the admin experience.
Comment #8
acbramley commentedThis is blocked behind 2 issues now. I'm also personally not a fan of moving node/add under admin/content for reasons described in #5