Skip to content
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

[Issue] Property "ShowDefaultNotificationMessage" does not have accessor method #29707

Open
4 tasks
m2-assistant bot opened this issue Aug 20, 2020 · 5 comments
Open
4 tasks
Labels
Area: Product Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.

Comments

@m2-assistant
Copy link

m2-assistant bot commented Aug 20, 2020

This issue is automatically created based on existing pull request: #26056: Property "ShowDefaultNotificationMessage" does not have accessor method


Description (*)

If you want create queue which will triggered whem you will save product in the admin (I created plugin afterSave for the Magento\Catalog\Model\ResourceModel\Product::save()), you will get critical error - Property "ShowDefaultNotificationMessage" does not have accessor method "setShowDefaultNotificationMessage" in class "Magento\CatalogInventory\Api\Data\StockItemInterface". Even if you do not use this interface in your extension, you still get an error.

Fixed Issues (if relevant)

Manual testing scenarios (*)

  1. Create simple rabbitmq queue extension
  2. Create plugin afterSave for the Magento\Catalog\Model\ResourceModel\Product::save()
  3. Set up consumer
  4. Save product in the admin panel
  5. Run php bin/magento queue:consumers:start YourConsumerName
  6. Got error)

Questions or comments

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 are green)
@ghost ghost added this to Ready for QA in Community Backlog Aug 20, 2020
@ghost ghost moved this from Ready for QA to PR In Progress in Community Backlog Aug 20, 2020
@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Aug 20, 2020
@lenaorobei lenaorobei added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Aug 20, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Development in High Priority Backlog Oct 20, 2020
@ghost ghost removed this from PR In Progress in Community Backlog Oct 20, 2020
@ghost ghost removed this from Ready for Grooming in Low Priority Backlog Oct 20, 2020
@engcom-Bravo engcom-Bravo added Area: Product Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Aug 25, 2021
@github-jira-sync-bot github-jira-sync-bot removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Aug 25, 2021
@github-jira-sync-bot
Copy link

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

@engcom-Bravo engcom-Bravo added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Aug 25, 2021
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.magento.com/browse/AC-997 is successfully created for this GitHub issue.

@m2-assistant
Copy link
Author

m2-assistant bot commented Aug 25, 2021

✅ 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.

@crippsy14
Copy link

Just to confirm, this is still an issue. Can I confirm if the accessor method is being added into the interface?

@mamsincl
Copy link
Contributor

mamsincl commented May 29, 2024

still issue, please

freshly duplicated on 2.4.6-p5 - product pushed to queue initially and failed to hydrated back is obtained by productRepository in adminhtml area

update:
as a quick workaround, resetting the related extension attribute (since related interfaces/classes are marked as deprecated, really no see any chance of getting any official solution)

$product->getExtensionAttributes()->setData('stock_item', null);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Product Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
High Priority Backlog
  
Ready for Development
Development

Successfully merging a pull request may close this issue.

6 participants