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.
Noticed in #2004428-1: Less ugly operations altering
Problem/Motivation
admin/structure/taxonomy
Error message
Notice: Undefined offset: 3 in _menu_translate() (line 757 of core/includes/menu.inc).
Symfony\Component\Routing\Exception\ResourceNotFoundException: in Drupal\Core\Routing\RouteProvider->getRouteCollectionForRequest() (line 122 of /Users/ctheys/foo/drupal/core/lib/Drupal/Core/Routing/RouteProvider.php).
this module passes testbot because we dont have test for taxonomy listing page to see if the translate link is in the operations drop button
Proposed resolution
TBD
Remaining tasks
- Write test for taxonomy listing.
- Propose and discuss a fix, link to related example if possible
.
Steps to reproduce
- Get config translation module
- install d8
- go to taxonomy listing admin/structure/taxonomy
- it works
- enable config translation
- reload page
- it has error
User interface changes
No.
API changes
Not expected.
Comment | File | Size | Author |
---|---|---|---|
#5 | config_translation.taxonomy_admin_page_error.2004690-5.patch | 1.84 KB | Kristen Pol |
#2 | i18n-config-trans-taxonomy-devel.png | 141.58 KB | Kristen Pol |
Comments
Comment #1
Kristen PolUsing devel I see that the route_name is:
config_translation.item.admin.structure.taxonomy._taxonomy_vocabulary_
Whereas if I go to views, these are like:
views_ui.list
Maybe that helps someone?
Comment #2
Kristen PolI guess somehow it's thinking it's on the translate version of the page when it's not. See the devel screenshot:
Ignore the "ooga" in the route_name... that was just me trying to see where it was set ;)
Comment #3
Kristen PolI'm thinking that maybe:
needs to be:
but it doesn't solve the error.
Comment #4
Kristen PolI figured it out... patch coming soon.
Comment #5
Kristen PolHere's a patch. Now the page comes up and there's a translate link in the list but if you go to that translate page, there is nothing there (should be follow up issue). I don't see any code for the taxonomy translate page unless it's supposed to auto-magically happen in a generic way.
Comment #6
Gábor HojtsyLooks like the path issue is due to https://drupal.org/node/1986784 change in core. The form likely also changed under us at some point. Good catches! Committed this patch. #2004710: Add tests for block, menu, vocabulary and views listings has tasks to add tests for this and other forms.
Comment #7
Kristen PolGood news that the patch at https://drupal.org/node/2004780#comment-7474128 fixes the errors I saw when going to the translate page for the vocabulary. Woohoo!