Open lytesaber opened 1 year ago
Hi @lytesaber. Thank you for your report. To speed up processing of this issue, 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:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. @magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://ef8fd27d2aff099c51a28c3eb3ba4a89.instances-prod.magento-community.engineering Admin access: https://ef8fd27d2aff099c51a28c3eb3ba4a89.instances-prod.magento-community.engineering/admin_fb54 Login: db1ec386 Password: f6de9224fc86
Hi @lytesaber,
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.
Steps to reproduce
It is working fine while creating product from admin manually.
When we create product via API Both Meta Title and Meta Description fields on the newly created product are blank.
Hence Confirming this issue.
Thanks.
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-8780 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Preconditions and environment
Steps to reproduce
Expected result
New product is created with both Meta Title and Meta Description fields based on the Product Fields Auto-Generation mask configuration.
Expected Meta Title Value: Example Product | Test Store
Expected Meta Description Value: Example Product at Test Store. Free delivery on orders over $75.
Actual result
Both Meta Title and Meta Description fields on the newly created product are blank.
Additional information
Product Fields Auto-Generation feature works for the product created manually in the Magento admin panel however not for products created programmatically via the API. Using the product fields auto-generation feature is still required even when syncing in new products from external POS or ERP systems which don't usually store website specific meta data.
Release note
No response
Triage and priority