Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
routing system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
5 May 2013 at 23:11 UTC
Updated:
29 Jul 2014 at 22:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tim.plunkettOkay, found the cause. It was my recent fix for _menu_translate().
Comment #2
Crell commentedIf the request doesn't match, do we want to continue silently? Or wouldn't that mean that there's nothing there, so we always want to disallow access to the link? I'm not sure, since that would then imply links to broken pages simply never show up at all... Hm.
Either way, IF we keep the empty catch statement then it needs to be documented as to why it's empty.
Comment #3
tim.plunkettWell if this passes, then we're better off doing it this way anyway.
Comment #4
tim.plunkettThis is a direct follow-up to #1938960: _menu_translate() doesn't care about new routes, it turns out. Sorry for the extra noise.
Comment #5
Crell commentedSince _menu_translate() is on the list of things to remove once the old routing system is removed, this seems fine to me.
Comment #6
dawehnerI'm wondering whether http://api.symfony.com/2.1/Symfony/Component/Security/Core/Exception/Acc... could be thrown as well.
Comment #7
Crell commentedWe don't have the Security component available, so no. :-)
Comment #8
alexpottCommitted 081af87 and pused to 8.x. Thanks!
Took the liberty of organising the use statements in menu.inc as per standards...