When using /content/versionview/ there will be displayed a warning about a translation mismatch, if the ContentObjectLocale is not located in settings/siteaccess/<name>/site.ini.
But for large sites with many siteaccess or many different servers (test, development, production, ...) it is a common practice to keep the files in settings/ as small as possible and move as much as possible into settings extensions. The following commons cases are not covered for now and will result in a warning displayed:

• There is a global setting of ContentObjectLocale in settings/override/site.ini because the whole site is in one language
• There is a global settings of ContentObjectLocale in extension/<name>/settings/site.ini because the whole site is in one language and the settings are used independent from the current server
• There are settings of ContentObjectLocale in extension/<name>/settings/siteaccess/<name2>/site.ini because the content locales of the site accesses are different, but they do not change and are thus independent from the current server

The patch fixes this by implementing the following logic, based on the correct settings override chain:

• For each given site access:
• If ContentObjectLocale exists in settings/siteaccess/<name>/site.ini(.append)(.php), use that.
• Else if ContentObjectLocale exists in extension/<name>/settings/siteaccess/<name2>/site.ini(.append)(.php), use that.
• Else read global value for ContentObjectLocale. (This will automatically be read from extension/<name>/settings/site.ini(.append)(.php) if existing, or fall back to settings/override/site.ini(.append)(.php) or even settings/site.ini.)

  Steps to reproduce

• Put the ContentObjectLocale somewhere else than in settings/siteaccess/<name>/site.ini
• If it exists in that location, comment or remove it from there
• Test /content/versionview/ in the 3 different cases mentioned above