I think I may have stumble onto a bug here.
My DEV and QA environments have the exact same setup, but in DEV I was able to create global blocks and translate them. So I went looking in the database.
There I found that on the QA site, there was an entry in tblContentLanguageSettings with fkContentID = 1 and Active = 0.
So to reproduce on DEV, I went to language settings for Root, selected a language and saved. Now I could only create block in that language. Then I went to Root language settings again and removed the checkbox. Now I could not create any blocks.
So the bug seems to be: If Root has no active languages, but has deactivated languages, then you cannot create global blocks.
Surely this is not intended behaviour?
Hi Morten, I think you should create a developer support ticket about that - and please share the result here ;-)
I've created a ticket now, so we will see what they say.
Still I would like to know what the best practice for language settings is, if anyone knows?
I'm looking for what the best practice is for setting up the Language Settings in EPiServer.
Given a page tree that looks like this:
If SiteA should have english and danish and SiteB english and french, how would you set up the lanugages?
What we have done tight now is to assign languages on the "Site* root" pages, and on the top Root, there are no languages. But this seems to give us problems with creating shareable blocks, because they apparently inherit from "Root"?
Would the correct approach be to assign all languages to the top "Root", and then let each site define a narrower language set if needed?
Thank you for any input you have on this.