Skip to content

[Issue] Use current sore id for category runtime cache #39310

Closed
@m2-assistant

Description

@m2-assistant

This issue is automatically created based on existing pull request: #36394: Use current sore id for category runtime cache


Description (*)

This is shorter PR version of https://github.com/magento/magento2/pull/34226/files that only fixes main issue and does not include suggested performance improvements.

When emulation is used or custom code saves the category in different stores, the object stored in runtime might be from wrong store to that causes data override.

Related Pull Requests

Fixed Issues (if relevant)

  1. Category data is changed after saving category link in a loop for different stores #22063
  2. Category eav values are overwritten with default store Values #32478

Manual testing scenarios (*)

  1. ...
  2. ...

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)

Metadata

Metadata

Assignees

Labels

Area: CatalogComponent: CatalogIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2A defect with this priority could have functionality issues which are not to expectations.Priority: P3May be fixed according to the position in the backlog.Progress: doneReproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions