Multilanguage Global Area not working1 user found helpful
However, I like the default "Home" (so the most top level page, the homepage with ID "1"), to be a locale content section. So by default, "/" is my English language. Beneath these are some other languages. It seems that if I do this, my global areas stop to function for only the language from the top level (English in this situation). Upon adding a block, I get the following:
call_user_func_array() expects parameter 1 to be a valid callback, class 'Concrete\Core\Permission\Key\AddBlockBlockTypeKey' does not have a method 'canAddBlock'
Is there any way we can fix that? Is this just impossible with concrete5, am i doing something stupid? It seems only this breaks if I do this method for the "Home" page. If I do this one level lower, everything seems to work.
We had a report from the user similar to this.
Page Type's Default Block has the similar issue.
Since they live outside the language section, the user is having hard time adding language specific stacks.
Perhaps, Page Type itself should support multilingual like stack and global area?
Again, they only show on pages when I don't put the "Home" (root) page as the English locale. So probably it's checking against real pages and not against the root (HOME_CID) or something, so it seems.
Maybe I didn't get the structural thinking of this CMS. But it is already hard to get a usefull tutorial entry point from the concrete5 homepage. It is not well structured and it"s confusing me where to find what. There should be somewhere a tutorial starting with "installation", then next setup your CMS (main useres, language, themes, add-ons, etc.), and then create and manage content. But I cant find find anything usefull and even not version dependent.
So I'm lost with a much promizing CMS with already difficulties by start up.