Today I was on
admin/config/development/configuration/single/export
(the configuration export page).

To get there, I went to:
Manage (top black bar) > Configuration (white menu bar) > Development (find this section, not actually a click) > Configuration management (click link) > Single import / export (click local task tab) > Export (click local action)

But the breadcrumb on the page shows, confusingly:

Home > Administration > Configuration > Development > Synchronize

Here's a screen shot:
Screen shot of breadcrumbs on admin/config/development/configuration/single/export

This is just wrong:
- Manage is shown as Administration
- Configuration management is completely missing from the trail.
- Instead of showing the local task tab I'm actually underneath (Single import / export), it is showing the default local task (Synchronize).

This is very broken.

Beta phase evaluation

Reference: https://www.drupal.org/core/beta-changes
Issue category Bug because of errors with the display of a breadcrumb.
Issue priority Major because the Configuration Management breadcrumb for subtasks was broken.
Prioritized changes The main goal of this issue is usability.
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

In general the breadcrumb uses the route titles not the menu titles. Does that mean we should update some of the menu links like "configuration" => "configuration managment".

- Instead of showing the local task tab I'm actually underneath (Single import / export), it is showing the default local task (Synchronize).

well this is how it is. The default breadcrumb is now path based, which means we no longer care about local tasks like in D7.
Under the current code this is how it is intended to work but I can see why we have to change this behavior or rather let contrib solve it.

jhodgdon’s picture

I do not think "let contrib solve it" is a good solution. This is broken in Core. Either Core should not put out breadcrumbs (because it cannot figure out how to do it), or Core should put out correct breadcrumbs.

Scott Weston’s picture

FileSize
116.11 KB
126.84 KB
483 bytes

The attached patch and file should address the confusion on the breadcrumbs on this page. After speaking with @crell, @yoroy, and @bojhan, it's agreed that breadcrumbs are working as intended. The patch updates the title of the route admin/config/development/configuration/synchronize to "Configuration management", which will help the breadcrumbs on admin/config/development/configuration/full/import and admin/config/development/configuration/single/import.

rklawson’s picture

Issue summary: View changes
Scott Weston’s picture

Status: Active » Needs review
rklawson’s picture

Worked with @scottweston to triage and DrupalCon LA Sprint. See #3 and issue summary.

jmarkel’s picture

Status: Needs review » Needs work

Fixing this individual case - or, I should say, kinda-sorta fixing it (since the local task navigation is still left as an exercise for the student) is necessary but not sufficient - it was presented as an example of the issue, not as the issue itself.

Breadcrumbs are (or at least were originally intended to be) UX enhancers. If they don't adequately describe a user's path to a page, they serve no useful purpose since they don't really show how to reproduce the way there but only a way to get back - and the back-arrow works at least as well for that.

ohthehugemanatee’s picture

Status: Needs work » Needs review

Bumping this back to "needs review", because according to the issue description and comment #3 - with consultation from @crell, @yoroy, and @bojhan - the issue *is* about this isolated case. Core is working as intended.

@jmarkel If you feel that there's a larger issue with path-based breadcrumbs as the default, that's a much bigger discussion for a separate issue.

ohthehugemanatee’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
19.17 KB

Tested working for me. Applied the patch and visited admin/config/development/configuration/ to see the "Configuration Management" breadcrumb. Then visited admin/config/development/configuration/single/export to make sure it was still there.

breadcrumb working

jmarkel’s picture

I strongly disagree with RTBCing this - the issue title says "Very confusing breadcrumbs on deep admin pageS" not "Very confusing breadcrumbs on the Configuration Management page."

Based not only on the summary but from comment #2 the intent of this issue was fairly clearly meant to describe a more general issue with breadcrumbs as implemented in D8.

yoroy’s picture

Status: Reviewed & tested by the community » Needs review

It's true that there are more pages and sections in admin where the same type of confusion happens.

Is the way this patch fixes this particular instance the right way? If so, we can:

1. Make inventory of all places where things go wrong and fix it all in one patch. Will be very hard to do
2. Repurpose this issue, make it a meta issue for "Fix all breadcrumbs" and create a new issue for config management section and upload this patch there
3. Edit: Keep this issue as is, and create a new meta for collecting all other instances.

If this way of solving things is not the right way, we need to first define what the correct way to go about it it.

jmarkel’s picture

Another possibility (which I admit not to have investigated yet) is to find a generalized way to make breadcrumbs more reflective of menu titles rather than being route/path based. I understand that this is currently working as intended - but that's not to say that it works in a user-friendly way.

xjm’s picture

(Saving proposed issue credit for discussion and triage participants at LA.)

jhodgdon’s picture

Status: Needs review » Needs work

Setting to Needs work because this doesn't really solve the whole problem.

jhedstrom’s picture

Status: Needs work » Needs review

I'd advocate for fixing small pieces as they are discovered, rather than trying to fix the whole problem this close to a release.

dawehner’s picture

Status: Needs review » Needs work

Well, then the small bit should be moved to its own issue.

jhedstrom’s picture

Title: Very confusing breadcrumbs on deep admin pages » Very confusing breadcrumbs configuration management admin pages
Status: Needs work » Needs review
Parent issue: » #2569799: [meta] Fix confusing breadcrumbs on deep admin pages
dawehner’s picture

Well, I think this issue was about the fact that our breadcrumb system is not optimized for our admin usages.

Truptti’s picture

FileSize
25.44 KB
64.96 KB

Applied the patch drupal-config-breadcrumb-confusion-2310175-3-D8.patch and visited 'admin/config/development/configuration/single/import' but the breadcrumb is still the same 'Home> Administration Configuration >Development >Synchronize'

Attached snapshot for reference.

Truptti’s picture

Status: Needs review » Needs work
jhodgdon’s picture

The problem is that pretty much ***every*** core admin breadcrumb is confusing, if there is any depth to the navigation, and I think that they all have "Administration" instead of "Manage" as the top-level breadcrumb, as reported here, and it is not even fixed in this patch.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dawehner’s picture

One possible bugfix could be to implement a menu tree based breadcrumb for /admin paths, but use the routing based ones for all the other URLs.

jhodgdon’s picture

We have to first decide whether this issue is about just these particular pages or all admin pages. If it's about all admin pages, then we should close the parent issue as a duplicate. If it's about just this page (or just the pages in the Configuration Management section), then the current patch will probably work.

But this is going to be a problem on any set of pages that have local tasks, if the main local task's title is not the same as the group's title.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

apaderno’s picture

Version: 8.6.x-dev » 8.8.x-dev
Issue tags: -breadcrumb +breadcrumbs

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

larowlan’s picture

Triaging for Bugsmash

pooja saraah’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
FileSize
489 bytes
451 bytes

Reroll patch against Drupal 10.1.x
Attached patch against Drupal 10.1.x

pooja saraah’s picture

smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative

Was tagged for issue summary in #39 which still needs to happen.

Also has 0 test coverage

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.