Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport] Declare module namespace before template path name(Magento_Sales::order/info.phtml). #16475

Conversation

gelanivishal
Copy link
Contributor

Original pull request

#16206

Description

When we override block info(Magento\Sales\Block\Order\Info) to my custom module.
It throws an error and finding order/info.phtml in my custom module.
I tried to extend Block Magento\Sales\Block\Order\Info from my custom module.

1 exception(s):
Exception #0 (Magento\Framework\Exception\ValidatorException): Invalid template file: 'order/info.phtml' in module: 'Vendor_Module' block's name: 'sales.order.info'

Fixed Issues (if relevant)

  1. Declare module namespace before template path name.

Manual testing scenarios

  1. I override info block
<preference for="Magento\Sales\Block\Order\Info"
				type="Vendor\Module\Block\Order\Info" />

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@gelanivishal gelanivishal changed the title Update Info.php [Backport] Declare module namespace before template path name(Magento_Sales::order/info.phtml). Jul 1, 2018
@magento-engcom-team magento-engcom-team added this to the Release: 2.1.15 milestone Jul 2, 2018
@magento-engcom-team magento-engcom-team merged commit 18f255b into magento:2.1-develop Jul 2, 2018
magento-engcom-team pushed a commit that referenced this pull request Jul 2, 2018
@magento-engcom-team
Copy link
Contributor

Hi @gelanivishal. Thank you for your contribution.
We will aim to release these changes as part of 2.1.15.
Please check the release notes for final confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants