Posted by Dave Reid on January 22, 2010 at 8:06pm
2 followers
| Project: | Drupal core |
| Version: | 7.x-dev |
| Component: | menu system |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
There are several instances of losing breadcrumbs in core. One that just stuck out to me was on the URL alias edit form. The local 'action' Add URL alias has nice breadcrumbs, but the 'Edit' callback does not. This is a *major* WTF for our users.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| screenshot_038.png | 41.31 KB | Ignored: Check issue status. | None | None |
| screenshot_039.png | 62.08 KB | Ignored: Check issue status. | None | None |
| screenshot_040.png | 52.72 KB | Ignored: Check issue status. | None | None |
Comments
#1
Also note how the tabs disappeared on the second/callback screenshot.
#2
Huh, I'm not getting the tabs either way on a fresh install, but I can confirm the breadcrumb problem. Also, I don't see in the menu code where the "Patterns" and "Settings" tabs come from -- what path do they go to for you?
#3
It's an experimental version of pathauto for D7 I'm working on. I'll try and find an example of just core code that this happens on with tabs disappearing.
#4
The tab thing I think you might want to put in a separate issue anyway. The breadcrumb problem I'm pretty sure is unrelated, and it is very widespread (when editing vocabs, terms, menu items, etc.).
It's looking like it's happening because when menu_set_active_trail queries the menu_links table, it's searching that table for the menu being used using the full qualified path, e.g., "admin/config/search/path/edit/1", which of course is not going to return a result from that table. This is probably an issue for a menu guru, but I'm still digging for the fun of it.
#5
Gah, found the original issue at #576290: Breadcrumbs don't work for dynamic paths & local tasks
#6
This simple fix seems to resolve the breadcrumb problem and a manual test looks good. Let's see how the testing bot does.
#7
Ah. Heh.