Skip to content

Fix wrong reference in google analytics module layout xml #18290

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

Merged
merged 1 commit into from
Oct 3, 2018
Merged

Fix wrong reference in google analytics module layout xml #18290

merged 1 commit into from
Oct 3, 2018

Conversation

sambolek
Copy link
Contributor

@sambolek sambolek commented Sep 27, 2018

Description

Simple change of reference (referenceContainer to referenceBlock) for Google Analytics module.

Fixed Issues (if relevant)

  1. Magento 2.2.5: Google Analytics not added to head correctly #16497 Magento 2.2.5: Google Analytics not added to head correctly

Manual testing scenarios

  • Observe "head.additional" is created as block app/code/Magento/Catalog/view/frontend/layout/default.xml
  • Observe "google_analytics" block is added to storefront by "referenceContainer" in app/code/Magento/GoogleAnalytics/view/frontend/layout/default.xml

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)

@magento-engcom-team
Copy link
Contributor

Hi @sambolek. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me $VERSION instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

Copy link
Member

@slavvka slavvka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although referenceContainer works perfectly with blocks (at least on my instance), I do approve the fix to avoid inconsistencies with overriding it.

@magento-engcom-team magento-engcom-team added this to the Release: 2.3.1 milestone Sep 27, 2018
@magento-engcom-team
Copy link
Contributor

Hi @slavvka, thank you for the review.
ENGCOM-3058 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

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

@slavvka
Copy link
Member

slavvka commented Oct 3, 2018

Hi @sambolek , we need the fix to be delivered also to 2.2-develop branch so please don't forget to port this PR to 2.2-develop; you can do it easily using the Porting Tool, https://devdocs.magento.com/guides/v2.2/contributor-guide/contributing.html#porting-tool

@sambolek
Copy link
Contributor Author

sambolek commented Oct 4, 2018

Hi @slavvka ,
thanks for the help - made a pull request to 2.2-develop as well now.

@slavvka
Copy link
Member

slavvka commented Oct 4, 2018

@sambolek Thank you!

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