Skip to content

Remove area emulation from media-content:sync command #29753

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

Conversation

jmonteros422
Copy link
Contributor

Description (*)

This PR Removes area emulation from \Magento\MediaContentSynchronization\Console\Command\Synchronize::execute

Fixed Issues (if relevant)

  1. Fixes Remove area emulation from media-content:sync command adobe-stock-integration#1784: Remove area emulation from media-content:sync command

Testing

  1. Add some images from media gallery to the content of category, product, page and block
  2. Clear media_content_asset database table
  3. Run media-content:sync command
  4. Verify all Used In links are correctly displayed in the asset details

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)

…a-content:sync command - remove area emulation
@m2-assistant
Copy link

m2-assistant bot commented Aug 26, 2020

Hi @jmonteros422. Thank you for your contribution
Here is 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

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

@jmonteros422
Copy link
Contributor Author

@magento run all tests

@BarnyShergold BarnyShergold self-assigned this Aug 26, 2020
BarnyShergold
BarnyShergold previously approved these changes Aug 26, 2020
@magento-engcom-team
Copy link
Contributor

Hi @BarnyShergold, thank you for the review.
ENGCOM-8081 has been created to process this Pull Request
✳️ @BarnyShergold, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@jmonteros422 jmonteros422 changed the title [WIP]#1784: Remove area emulation from media-content:sync command #1784: Remove area emulation from media-content:sync command Aug 27, 2020
@engcom-Bravo engcom-Bravo self-assigned this Aug 27, 2020
Copy link
Contributor

@engcom-Bravo engcom-Bravo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ QA Failed

The synchronization works properly only once. But if you clear the media_content_asset table twice, the Used in will not display any records
Manua testing steps:

  1. Add some images from media gallery to the content of category, product, page and block
  2. Clear media_content_asset database table
  3. Run media-content:sync command
  4. Verify all Used In links are correctly displayed in the asset details
  5. Clear media_content_asset database table one more time
  6. Run media-content:sync command
  7. Verify all Used In links are correctly displayed in the asset details

AR: The Used in section is not displayed in image details

@sivaschenko sivaschenko added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Aug 27, 2020
Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @jmonteros422 ! Please see my comment

@@ -58,12 +48,7 @@ protected function configure()
protected function execute(InputInterface $input, OutputInterface $output)
{
$output->writeln('Synchronizing content with assets...');
$this->state->emulateAreaCode(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This emulation is used for Magento to generate proper links when searching for content usages. When removing the emulation - the links generation should be fixed

@ghost ghost assigned sivaschenko Aug 27, 2020
@ghost ghost dismissed BarnyShergold’s stale review August 27, 2020 11:35

Pull Request state was updated. Re-review required.

@sivaschenko sivaschenko added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. and removed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. labels Aug 27, 2020
Copy link
Contributor

@engcom-Bravo engcom-Bravo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes test

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Synchronization is not executed for entities that have not been updated since last sync execution, can you please update the entity before performing the second table cleanup and sync

@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, thank you for the review.
ENGCOM-8081 has been created to process this Pull Request
✳️ @sivaschenko, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@sivaschenko sivaschenko added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Aug 27, 2020
@engcom-Bravo
Copy link
Contributor

✔️ QA Passed

Manual testing steps

  1. Add some images from media gallery to the content of category, product, page and block
  2. Clear media_content_asset database table
  3. Run media-content:sync command
  4. Verify all Used In links are correctly displayed in the asset details

The media content synchronization is covered in several scenarios on cucumber studio. There is no need to create a separate for this PR.

@engcom-Bravo engcom-Bravo added Progress: testing in progress QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed Progress: extended testing labels Aug 28, 2020
@sivaschenko sivaschenko changed the title #1784: Remove area emulation from media-content:sync command Remove area emulation from media-content:sync command Aug 31, 2020
@BarnyShergold BarnyShergold removed their assignment Sep 1, 2020
@magento-engcom-team magento-engcom-team merged commit eb00722 into magento:2.4-develop Sep 2, 2020
@m2-assistant
Copy link

m2-assistant bot commented Sep 2, 2020

Hi @jmonteros422, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: MediaContentSynchronization Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Project: ASI QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Remove area emulation from media-content:sync command
5 participants