Adding validation for avoiding cleaning the 'cat_p' cache when saving…

[Rus0]

… a product in frontend

Description (*)

Adding validation for avoiding cleaning the 'cat_p' cache when saving a product in frontend, adding a new variable for catching the changes in the afterCommitCallback once it is saved, since hte hasDataChanges already is false once it reaches the AbstractModel original function

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Performing Product Resource save action on frontend area invalidates cache of all products #40074

Manual testing scenarios (*)

1. Enable debug logging for monitoring cache invalidation log entries
2. Create a new module
3. Create a frontend area router and Controller e.g. custom/index/index
4. Implement product saving action in Controller
5. Use $product->save() or $productResource->save($product) (check using both to confirm)
6. Start monitoring cache_invalidate entries e.g. with tail -f -n 0 var/log/debug.log | grep "cache_invalidate"

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)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @Rus0. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[Rus0]

@magento run all tests

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Hello @Rus0,

Thank you for your contribution!

We are currently discussing this PR with our PO, till the time we are moving this PR on hold.

Thank you