Multilanguage Global Area not working

Permalink 1 user found helpful
First let me say, global areas work fine when I set pages up like /en, /de, /fr and assign these pages as a locale.

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.

View Replies:
andrew replied on at Permalink Reply
Hmm this is interesting. We only added the ability to make the home page a localeable section fairly recently so it wouldn't surprise me if there were problems with that. I haven't seen this specific issue though. Is there a reason why you can't make /en a locale section and set up redirection to that by default.
ramonleenders replied on at Permalink Reply
I actually can make the homepage a locale, for "English" in my example. But the global areas on the pages in THIS language (English) don't seem to work. They got the error posted in the original post. All other languages have working global areas though. If I don't select the "Home" as my English locale, but a page deeper, the global area DOES work. So something is not working, when my root "Home" is set as a locale.
katz515 replied on at Permalink Reply
Oh, I would like to jump in this topic too.

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?

ramonleenders replied on at Permalink Reply
If I go to "Stacks & Blocks", click "View Global Areas" in the top right and edit the English one, I can add blocks. HOWEVER, these are not showing (on the page, within this admin page the blocks are showing).

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.
mlocati replied on at Permalink Reply
concrete5 8 won't suffer such problems
ramonleenders replied on at Permalink Reply
We don't have concrete5 version 8 yet, we are on version 7! Haha... would be awesome if this is possible with the current version, as some are still on version 6 even.
Resipisco replied on at Permalink Reply
I got a strange effect by setting the Home page to multilingual. The Header section disappear. If I try to edit it (add Block) I get the same erro message like you. I have the concrete5 version and I"m just started to use it, mean no page content (only the default pages).
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.