Problem/Motivation
PathProcessorLanguage::initProcessors is not sorting the methods by their weights and so they are called by ::processInbound and ::processOutbound not in a order defined by their weights.
This causes a problem, where one outbound processor might depend on another one or one might want to alter the options array before it is passed to the next outbound processor.
This is what we are doing in our current approach in #1810394: Site configuration with domain based language negotiation results in redirecting authenticated users to a different domain when accessing a content entity route for translation language different from the interface language and thus this issue is a blocker.
Proposed resolution
Sort the methods by weight in PathProcessorLanguage::initProcessors.
Remaining tasks
none
User interface changes
none
API changes
none
Data model changes
none
Comment | File | Size | Author |
---|---|---|---|
#3 | 2576945-3.patch | 2.83 KB | hchonov |
Comments
Comment #2
hchonovA possible fix.
Comment #3
hchonovOups... forgot to upload the patch.
Comment #6
Gábor HojtsyLooks good, makes sense to me :)
Comment #7
webchickCommitted and pushed to 8.0.x. Thanks!
Comment #9
Gábor HojtsyYay, superb.