Hi Jules, Thanks for the report !
We've had a similar issue before, which I thought was fixed; we'll need to investigate this a little further. In the meantime, there is a simple workaround: open the offending page(s) on your author instance. Doing so should trigger the creation of the missing "extras" node on that page. Now activate this page (so the missing "extras" node will be created on the public instance too) and the error message should disappear. [1] http://jira.magnolia-cms.com/browse/MGNLSTK-499 On Apr 21, 2010, at 2:31, Jules S. wrote: > > Dear magnolia developers, > > Today I also ran into a bug, that seem to affect the magnolia company > website, too. I searched the jira system, but did not find a related bug > report, so please have a look at mine at: > http://jira.magnolia-cms.com/browse/MAGNOLIA-3184 > > I have not learned much of the magnolia source code yet, because I > wanted to get in touch with this cms as an ordinary user. That is why I > can not send you a fix yet, a thousand pardons. > > What do you think about this problem? Why is there an "extra" component > that can not be accessed? > > Best Regards, > Jules > > > > > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
