Magento – Magento 2 System Log Errors

layoutmagento2

Just had a look at the var/log/system.log file and surprised to see the number of errors. I cleaned up the file and refreshed the website and it logged following errors:

[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'header.panel.wrapper' element cannot be added as child to 'header.container', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'header-wrapper' element cannot be added as child to 'header.container', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'navigation.sections' element cannot be added as child to 'page.top', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'top.container' element cannot be added as child to 'page.top', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'breadcrumbs' element cannot be added as child to 'page.top', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'footer' element cannot be added as child to 'footer-container', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'catalog.compare.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'sale.reorder.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'wishlist_sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'header.panel.wrapper' tries to reorder itself towards '', but their parents are different: 'header.container' and '' respectively. [] []
[2016-10-12 14:27:20] main.CRITICAL: Broken reference: the 'navigation.sections' tries to reorder itself towards '', but their parents are different: 'page.top' and '' respectively. [] []

Same behavior on a fresh installation with no custom theme!
Any idea to why these layout errors!!

Best Answer

From what i can tell the issue seems to be due to messy layouts and that are not getting moved or rendered correctly on certain pages.

The examples i have looked into so far is the catalog.compare.sidebar and sale.reorder.sidebar which are in the Magento Catalog module default.xml layout file however on the product page there is no sidebar so these fail to render. I believe this is default behaviour however as there is no sidebar on product pages and so this error is happening on even vanilla Magento installations.

So far i have tried removing the block from the product page but this does not help the error. Only thing i can think is to remove the block from the default.xml within a custom theme and add back into each page type individually on pages that do contain the sidebar.

Regarding the debug file

So the messages like this main.DEBUG: cache_invalidate in Magento 2 are not errors, there are only debug messages to tell that the cache is invalidated (which is not a problem nor an error).

Regarding the system file

So the messages like this Broken reference: the 'block1' tries to reorder itself towards 'block2' is not a real error either. As you can see from this github issue:

Ok, guys. There is no bug here ) Really. There are two reasons, why you all see such a logs.

Reason 1 People keep forgetting remove "before" and "after" attributes for blocks which have been moved to another parent, so those are no longer relevant. Internal ticket in progress MAGETWO-53410 and we will clean up legacy references soon.

Reason 2 As an example, let's take Such references mostly (if not all) reside in default.xml files (so will be applied to all pages without exclusions), while the container "sidebar.additional” is added by 2columns-left.xml layout only. So, on pages where different page layout is used, the reference will lead to nowhere, and you will see CRITICAL error logged (while it is not critical at all).

The tricky thing is that sometimes that could be a normal case and developer understands why it happens (if want to add a block to specific container to all pages on which target container available, and don’t need that block to be added to the pages where target container is not available).

Short excerpt from internal ticket description: "Stop logging such cases at all, or at least stop marking them as CRITICAL (ensure that it’s not logged in production mode). Also it will be helpful if logged message will say the URL of the page where target container is missed".

So, as you see, we still think that logging such "broken" references is a right thing to do, since some of them are really could be caused by misspells in layout files.

I reckon there was a lot of errors like this in the logs in the early stable releases as you can see from those two issues:

So if you wanna get rid of them, I reckon you should update to the last version. Seems like Magento fixed it in the develop branch but I'm not sure if the bug fixes are part of 2.0.8/2.1.1 already.

Magento 2 Adminhtml – Fix Custom Block Blank Page Issue

your file name and class name and xml class not matched

file name app/code/Vendor/Widget/Block/Adminhtml/SelectWidgetBlock.php

you xml will be

<referenceContainer name="content">
        <block class="Vendor\Widget\Block\Adminhtml\SelectWidgetBlock" name="vendor_widget.select" template="Vendor_Widget::selectwidget.phtml"/>
    </referenceContainer>

Best Answer

Related Solutions

Magento – Magento 2: Admin Attention Something went wrong

Regarding the debug file

Regarding the system file

Magento 2 Adminhtml – Fix Custom Block Blank Page Issue

Related Topic