Call to a member function addCrumb()

[lano-vargas]

I have encounter a small issue on new installation of Magento 2.1.7 regards to breadcrumbs.

step to recreate the issue is simple once install is susccesfull:

1- create custom Theme
2- create default.xml
3- add <referenceBlock name="breadcrumbs" remove="true" />
4- navigate to your Magento installation root url .../sales/guest/form/

5- error: 500

Log:
PHP Fatal error: Call to a member function addCrumb() on boolean in /Library/WebServer/Documents/dev/vendor/magento/module-sales/Helper/Guest.php on line 205

Comment or removing

/($breadcrumbs->addCrumb(
'home',
[
'label' => __('Home'),
'title' => __('Go to Home Page'),
'link' => $this->_storeManager->getStore()->getBaseUrl()
]
);
$breadcrumbs->addCrumb(
'cms_page',
['label' => __('Order Information'), 'title' => __('Order Information')]
);/

Will display the the page correctly.

Thank's
Juliano

[magento-engcom-team]

Hi @lano-vargas
thank you for the report. Would like submit a pull request with the fix? By this, you can participate in #SQUASHTOBERFEST

[magento-engcom-team]

The fix looks simple

[lano-vargas]

@magento-engcom-team I can't promise but will try and work on it this weekend.

I'm working on it #SQUASHTOBERFEST.

Thanks.

[lano-vargas]

@magento-engcom-team the "continuous-integration/travis-ci/pr" has errored with

"The job exceeded the maximum time limit for jobs, and has been terminated."

ref: https://travis-ci.org/magento/magento2/jobs/285215690

Please advice what to do next.
Thanks.

[lano-vargas]

@okorshenko Could you please restart build/trigger as mentioned here:https://stackoverflow.com/questions/17606874/trigger-a-travis-ci-rebuild-without-pushing-a-commit
Appreciate.

[orlangur]

@lano-vargas restarted, main CI source of truth is Bamboo runned internally, I'll let you know if there will be some issues revealed.

[lano-vargas]

@magento-engcom-team errored for the same reason as #11275 (comment)

[adrian-martinez-interactiv4]

@magento-engcom-team This issue should be closed, solved in PR #11382

[okorshenko]

the issue has been fixed and delivered to 2.2.2 branch. Will be available with 2.2.2 release

[magento-team]

Internal ticket to track issue progress: MAGETWO-81647

[magento-engcom-team]

Hi @lano-vargas. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1283 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

• 0742857
• fde512e
• e7d90de
• 6d4f36d
• 2e83a36
• 23b4aa1
• b50bfa8
• 04cd60d
• 75d5a05
• 5e02b15
• aad5ba6
• 3e32140
• 7898946
• a173e1c
• 41d0075
• dda19b2
• cba48cd
• 0c62caa
• 736f783
• 7569b70

The fix will be available with the upcoming patch release.