Hey Christian (@christianm),
thanks for your answer!
Let me ask more about No. 1, your suggestion made me to get more into the by default (setup) defined site root which is a normal Neos.NodeTypes:Page I guess? Where and how it is defined is still a little mysterious to me?? I like the idea to make a Shortcut out of it, but then other issues come up:
-
Home is active in the menu now, but I would have it in the URL as well, which would be okay for now but not really what I need in general.
-
Accessing the Footer-ContentCollection gives me difficulties! I am following the documentary to create it (Shared Footer), now since my site/root is only a Shortcut to the next page “home”, I need to access the Footer through finding the subpage first, as suggested in the last sentence in the Docs. To be precise how do these lines have to look to access the Footer on the Page: “home”?
footer = Neos.Neos:ContentCollection { nodePath = ${q(site).find('home').children('footer').property('_path')} collection = ${q(site).find('home').children('footer').children()} }
There are a couple of Discussions about this topic but none really answers the Exception some of us are facing… (eg.: Shared Footer I have tried variants of this too. It’s just still a little difficult to separate between my own incompetence and actual bugs in the System…
I can just guess, but it all seems to be related to the site error… When you install a Neos 3.1.1 without the Demo-Site and then run the “./flow node:repair” it shows a “Sites-Error” straight away!??
Right now I keep crashing my Neos, while trying to get some basic things to work. Many times I end up deleting my database just to make sure to start from scratch… I will split up those issues into smaller topics, but they keep coming up in relation to each other… I love Neos and while I got a lot working already keep realizing that I don’t really control the System yet (wanting to use it in production very very soon…)
Thanks!
Robin