Skip to content

Unable to render page when 'meta title' page config param is set #issue-2956 #15338

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

Closed
wants to merge 4 commits into from

Conversation

rainashikha
Copy link
Member

@rainashikha rainashikha commented May 19, 2018

Description

Fixed. Added a check to to see if returned content is object or not. As objects will never be converted to string and will throw error for str_replace at line 125

Fixed Issues (if relevant)

  1. Unable to render page when 'meta title' page config param is set #2956: Unable to render page when 'meta title' page config param is set

Manual testing scenarios

  1. Use the "Steps to reproduce" in original issue.
  2. View the source generated in browser.
  3. You will be able to see <meta name="title" content="some meta title"/> in source code.

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#2956

Fixed. Added a check to to see if returned content is object or not. As objects will never be converted to string and will throw error for str_replace at line 125
@magento-cicd2
Copy link
Contributor

magento-cicd2 commented May 19, 2018

CLA assistant check
All committers have signed the CLA.

@VladimirZaets
Copy link
Contributor

Hi, @rainashikha. Thanks for collaboration.
We have the fix this issue in current 2.3-develop
Can you please make the backport from 2.3 to 2.2-develop for code consistency?

Related commit(s):

@gelanivishal
Copy link
Contributor

@rainashikha Please sign our Contributor License Agreement before we can accept your contribution.

@sidolov
Copy link
Contributor

sidolov commented Jun 6, 2018

@rainashikha , I am closing this PR now due to inactivity.
Please reopen and update if you wish to continue.
Thank you for collaboration!

@sidolov sidolov closed this Jun 6, 2018
@rainashikha
Copy link
Member Author

i had got this message..

We have the fix this issue in current 2.3-develop
Can you please make the backport from 2.3 to 2.2-develop for code consistency?

so please let me know what is required from my end? are u merging this pull request? is anything pending?

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.

7 participants