6

I got this error in system.log:

main.CRITICAL: Broken reference: No element found with ID 'checkout.header.wrapper'

and the checkout page is blank.

  • Any Updates...? – Ayush Mittal Aug 29 '16 at 14:17
  • Please update more details, there is any customization? – Khoa TruongDinh Aug 29 '16 at 14:24
  • @AyushMittal have you resolved? – Bojjaiah Dec 15 '16 at 5:17
3

I solved this warning message in Magento 2.1.1:

Open your file (override file not in vendor) checkout_index_index.xml.

In line equals:

<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">

add layout="1column" property:

<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" layout="1column" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">

I found this solution here.

  • I'm getting this error while layout="1column" already existing. – Nitesh Feb 14 '17 at 7:20
  • @Nitesh please check system.log if error in other checkout xml. Post your log line here . Thanks !!! – Matt Bidas Feb 15 '17 at 20:41
1

The Broken Reference layout errors are nothing new and have been reported to Magento team numerous times by different people. I tried it on a fresh installation just to see whether it was my custom theme or changes that were causing it but with default luma theme without inheriting it I still get these errors.

I somewhat agree with @KAndy above that these errors can be ignored because according to Magento core team this was fixed in 2.1 but it's still going on and reported by numerous people. It doesn't affect the functionality of the system in any way (or it hasn't been reported by anyone yet) so it's not a priority for Magento core team hence for now it can be ignored. Of course my only concern is ever increasing size of the system.log file that will need to be cleaned up regularly other than that nothing to be overly concerned about.

Reference https://github.com/magento/magento2/issues/3507

-1

You can ignore it. It's not a critical error, this must be a warning.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.