-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Fix #20111 - display variables in popup while editing existing email template #22469
Fix #20111 - display variables in popup while editing existing email template #22469
Conversation
… email template
Hi @Bartlomiejsz. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
Hi @orlangur, thank you for the review. |
Hi @Bartlomiejsz ! Your fix provides next problem: Fatal Error message after insert variable to template Steps to reproduce:
Actual result: We've got fatal error message |
@magento-engcom-team give me 2.3-develop instance |
Hi @Bartlomiejsz. Thank you for your request. I'm working on Magento 2.3-develop instance for you |
Hi @Bartlomiejsz, here is your Magento instance. |
@magento-engcom-team give me test instance |
Hi @Bartlomiejsz. Thank you for your request. I'm working on Magento instance for you |
Hi @Bartlomiejsz, here is your new Magento instance. |
@stoleksiy this error is not caused by those changes. You can see exactly same error when you follow those steps on 2.3-develop instance:
This is because as result you have incorrect html being saved (variable is injected before <!DOCTYPE and this have nothing to do with changes from PR. This even have nothing to do with injecting variables because customer can write any dummy text before header in template and result will be the same I believe. |
@Bartlomiejsz Thanks for the clarification! |
Hi @Bartlomiejsz, thank you for your contribution! |
…isting email template #22469
After this fix, template variables are missing when creating a new template: https://prnt.sc/nxj254 |
Description (*)
In this PR I tried to fix #20111 after it was probably abandoned.
Fixed Issues (if relevant)
Manual testing scenarios (*)
Contribution checklist (*)