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

MAGETWO-99236 Fix for #22063 Category data is changed after saving category linkfor different stores #34226

Open
wants to merge 18 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

ilnytskyi
Copy link
Contributor

Description (*)

When there is a loop going through a few products and linking those products to categories. Some categories get data copied from another store.

Load a category from the default store instead of taking the last cached from CategoryRepository.

I think it would also be better to save the category via its repository. Unfortunately the CategoryRepository ignores posted products

$category->setPostedProducts($productPositions);

(probably a case for another bug)

Related Pull Requests

Fixed Issues (if relevant)

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

Manual testing scenarios (*)

  1. Create a few stores
  2. Give different descriptions and short descriptions to a category in each store.
  3. Loop through different stores e.g. with emulation or just load categories based on product store id
  4. Link a product to a category.
  5. Category has correct data (data was not copied from the category instance that loaded in different store)
\Magento\Catalog\Model\CategoryRepository::get

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
Copy link

m2-assistant bot commented Oct 2, 2021

Hi @ilnytskyi. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ 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

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@ilnytskyi
Copy link
Contributor Author

@magento run Integration Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@mrtuvn
Copy link
Contributor

mrtuvn commented Oct 3, 2021

Can you re-check fails in static (maybe code styles check)
Thanks you for your works

@ilnytskyi
Copy link
Contributor Author

Yes, but I see there other problems with this case. It requires additional debug.

…ing link, improve test case, improve test fixtures
@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run Integration Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi ilnytskyi changed the title MAGETWO-99236 Fix for #22063 MAGETWO-99236 Fix for #22063 Category data is changed after saving category linkfor different stores Aug 30, 2022
@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run Integration Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

up

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

# Conflicts:
#	app/code/Magento/Catalog/Test/Unit/Model/CategoryLinkRepositoryTest.php
@ilnytskyi
Copy link
Contributor Author

@magento run all Tests

@m2-community-project m2-community-project bot added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Catalog Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Priority: P3 May be fixed according to the position in the backlog. Progress: pending review Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
4 participants