When configuring language path prefixes, there may be only one empty path prefix, that of the site default language. The intention of this is to protect users from setting an empty prefix for something that would not end up being selected as a fallback in the negotiation, basically making that language inaccessible by path. However, we made the fallback language configurable, so that this would be the site default language is not necessarily true. So you may now end up with a configuration where you cannot change the fallback language and remove the prefix before going live unless you also modify the site default language, which is silly. That was the reason we separated the default and the fallback languages to begin with.
Either only validate that at most one path prefix may be empty or validate that that is for the fallback language configured in the negotiation (not the site default).
Agree on approach. Implement.
User interface changes
Limitation on which language may get an empty prefix may change depending on configuration.
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 86,839 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 86,130 pass(es). View