Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When you change the name (label) of your content type, your breadcrumbs still show the original content type name.
In the 2015 Usability study, one participant realized they named their content type "Session track" when they intended to name it "Session proposal". They edited the content type label to "Session proposal":
But then on the Manage fields page became confused when they saw "Session track" in the breadcrumb:
It was even more confusing because, as seen in the screenshot above, they created field called "Session track" after realizing that it should be a field and not a content type ...
Clearing the cache does not resolve this issue.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2513570-3.patch | 2.94 KB | tim.plunkett |
| #2 | basic-page-breadcrumb.png | 16.77 KB | lunk rat |
| #2 | basic-page-name.png | 17.36 KB | lunk rat |
| screenshot-umn6-4uzacmjokti24.us_.platform.sh 2015-06-28 14-05-05.png | 44.69 KB | lunk rat | |
| screenshot-umn6-4uzacmjokti24.us_.platform.sh 2015-06-28 14-03-36.png | 22.32 KB | lunk rat | |
Comments
Comment #1
lunk rat CreditAttribution: lunk rat commentedComment #2
lunk rat CreditAttribution: lunk rat commentedLooks like this even affects the built-in "Basic page" content type. Here it is in the listing:
Yet in the breadcrumb it's displayed as just "Page":
Comment #3
tim.plunkettHere's a test proving the bug.
Interestingly enough, renaming the machine name of the content type *does* fix the breadcrumb. That should help to find the cause.
This might be more wide-spread than just content types, but moving to node for now.
Comment #5
kevin.dutra CreditAttribution: kevin.dutra at Workday, Inc. commentedHmm, there might be two different bugs going on here. One aspect revolves around improper cacheability metadata. Looking at the cache tags that are applied (by checking the DB directly), I find
block_view config:block.block.seven_breadcrumbs rendered. No entity related cache tags at all.I can confirm that this does expand beyond just content types. It seems the same is true for any breadcrumb that is using the label of an entity. I haven't dug down to see whether the metadata just isn't being supplied or if it's not bubbling up correctly.
That being said, a cache rebuild does fix the problem for nodes (as an example). But since it doesn't fix it for content types, there must be something else coming into play too.
Comment #8
jonathanshawThis is partially duplicated by #2835018: The content type name in the backend breadcrumb should be Human name.
Comment #10
idebr CreditAttribution: idebr commentedAdded #2855636: Regression: incorrect human-readable name for content type as a related issue
Comment #12
jeromewiley CreditAttribution: jeromewiley commentedSubscribe. (on my D 8.3.6 site, I have updated a content type from "story" to "Story" and it's still showing "story")
Comment #14
kfritschefyi: the test from here is merged into #2607920: Breadcrumb render cache not invalidated when entity label changes
Comment #15
jonathanshawSo #2855636: Regression: incorrect human-readable name for content type is fixed and covers the same as #2835018: The content type name in the backend breadcrumb should be Human name. That would appear to address half this issue, and the other half is now covered by #2607920: Breadcrumb render cache not invalidated when entity label changes. So it looks like this can now be closed as a duplicate?
Comment #16
tstoecklerYes, I think that makes sense.