Content page PathNotFound exception returned by server

[dantleech]

After initially installing and initialising my webspace I go to the content page and - nothing happens.

A 500 is returned from the nodes endpoint because it is requesting a non-existant path.

• My admin locale is en
• The path it cannot find is /cmf/foobar_lo/routes/en
• Because my webspace is only configured for fr
• If I change my locale to de then it tries to get /cmf/foobar_lo/routes/de
• I only have en and de avialble as admin locales.

However, for some unknown reason, now it is working and pulled in /cms/foobar_lo/routes/fr.

So an issue: The default locale for the content page should not use locales which do not exist in the webspace.

And a question: Where do I define the admin locales? e.g. there is en and de but I cannot find where this is configured/hard-coded.

[danrot]

The problem is that we didn't built the functionality to get all the available locales yet.

And the admin locales are not defined anywhere, it just tries to load the translation file with the given locale from app/Resources/public/js/translations, and will currently fail, if the file does not exist.