broken references when viewing admin after initial install

[markshust]

These messages come up when going to the admin after a fresh install:

[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'global_notices' element cannot be added as child to 'global.notices', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'logo' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'logo' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'global.search' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'logo', but their parents are different: 'header' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'user' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'user' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'menu' element cannot be added as child to 'page.menu', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'breadcrumbs' element cannot be added as child to 'page.breadcrumbs', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'formkey' element cannot be added as child to 'page.formkey', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'page.title' element cannot be added as child to 'main.top', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'messages' element cannot be added as child to 'page.messages', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'page.actions.toolbar' element cannot be added as child to 'page.main.actions', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'page.actions.toolbar' tries to reorder itself towards '', but their parents are different: 'page.main.actions' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'locale.switcher' element cannot be added as child to 'footer', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'legal' element cannot be added as child to 'footer', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'page.loader' element cannot be added as child to 'backend.page', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'page.loader' tries to reorder itself towards '', but their parents are different: 'backend.page' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'requirejs-config' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'translate' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'head.components' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'head.calendar' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'system_messages' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'system_messages' tries to reorder itself towards '', but their parents are different: 'notifications' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'unread_system_messages' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'unread_system_messages' tries to reorder itself towards 'system_messages', but their parents are different: 'notifications' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'notification_window' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'notification.messages' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'notification.messages' tries to reorder itself towards 'user', but their parents are different: 'header' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'header.inner.left' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'header.inner.left' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'header.inner.right' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'header.inner.right' tries to reorder itself towards 'header.inner.left', but their parents are different: 'header' and '' respectively. [] []
[2015-09-04 20:14:41] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and '' respectively. [] []

[alankent]

Yes, I don't think this is a new problem, but the "CRITICAL" part is not good. I think what is going on is if you access a one column layout page, there are not as many containers present as the 2 and 3 column versions. 2 and 3 columns are actually the same layout file, just with different CSS to move things to the left or right - so identical containers are present. One column however does not have as many containers.

Just tossing around an idea quickly, one possible approach is to have a flag on containers so you can say "hidden". So the rendering library throws it away in one column mode still, but you have the same set of containers for all page layouts to stop these messages appearing.

(I have not discussed with core team yet, they might have some clever idea as well.)

Note: I have not verified this is the problem, but I think it is for some of the error messages at least. I guess could experiment by changing say the dashboard to 2 column mode and see if they go away when hitting the home page.

Another alternative is to just review if CRITICAL versus debugging level only.

[piotrekkaminski]

internal issue MAGETWO-43793

[davidalger]

Fixed. Please reopen if issue persists.

[nmallepally]

I see this error on 2.1v install , lot of broken reference in my system.log and cache invalidate in debug.log errors. attached a file for ref.
system.log.em.txt