-
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
Meta Description Auto generation copying page builder tags #36107
Comments
Hi @vandijkstef. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@magento give me 2.4-develop instance |
Hi @vandijkstef. Thank you for your request. I'm working on Magento instance for you. |
Hi @vandijkstef, here is your Magento Instance: https://2bc4eeb41888e69c2b930f938f4ebfc4.instances.magento-community.engineering |
Cannot verify currently as the page builder is not allowing me to drag-in any of the (layout) elements |
@magento give me 2.4-develop instance |
Hi @vandijkstef. Thank you for your request. I'm working on Magento instance for you. |
Hi @vandijkstef, here is your Magento Instance: https://2bc4eeb41888e69c2b930f938f4ebfc4.instances.magento-community.engineering |
Tried to verify again, above issue not resolved. Can't directly find an active issue on this. |
Hi @engcom-November. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-November, here is your Magento Instance: https://2bc4eeb41888e69c2b930f938f4ebfc4.instances.magento-community.engineering |
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-November, here is your Magento Instance: https://2bc4eeb41888e69c2b930f938f4ebfc4.instances.magento-community.engineering |
Hi @vandijkstef , Thank you for reporting and collaboration. |
Internal team is working on the fix |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-7425 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
❌ You don't have permission to export this issue. |
Preconditions and environment
Steps to reproduce
Expected result
Clean text-only output
Actual result
edit: This is the meta description field
Additional information
The workaround is to manually update it, but chances are high it is forgotten to properly update it, thus having NOTHING would be preferred as Google is actually showing some of this garbage in it's results
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: