By default and some miracle happening in the language detection/block/form management APIs the search form will use the language defined for the interface, not the language. Which means that if you are setting up a site, where the content language is different from the interface, the user will end up with a search form that shows on the fallback language configured for the interface.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | block_language_should-2720105-2.patch | 3.26 KB | snufkin |
| #4 | block_language_should-2720105-2.patch | 2.93 KB | snufkin |
| #3 | block_language_should-2720105-2.patch | 2.93 KB | snufkin |
| #2 | block_language_should-2720105-2.patch | 2.63 KB | snufkin |
Comments
Comment #2
snufkin commentedThe patch attached ensures that routes and t() functions retrieve the content language and use it.
Comment #3
snufkin commentedAdding the language to the cache context.
Comment #4
snufkin commentedFixing typo.
Comment #5
snufkin commentedAnd fixing the reference to the right class.
Comment #6
swentel commentedLet's see what the testbot thinks
Comment #16
swentel commentedcommitted and pushed, thanks!