Skip to content

Fix #30471 - Page layouts are hard-coded in Magento\Widget\Block\Adminhtml\Widget\Instance\Edit\Chooser\Container #31886

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

Bartlomiejsz
Copy link
Contributor

@Bartlomiejsz Bartlomiejsz commented Jan 28, 2021

Description (*)

This is a fix for #30471 issue

Related Pull Requests

https://github.com/magento/partners-magento2ee/pull/465

Fixed Issues (if relevant)

  1. Fixes Page layouts are hard-coded in Magento\Widget\Block\Adminhtml\Widget\Instance\Edit\Chooser\Container #30471

Manual testing scenarios (*)

Please check fixed issue for steps descrription

Questions or comments

Not sure if any kind of tests would fit here

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)

…ck\Adminhtml\Widget\Instance\Edit\Chooser\Container
@m2-assistant
Copy link

m2-assistant bot commented Jan 28, 2021

Hi @Bartlomiejsz. 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
  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

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jan 28, 2021
@Bartlomiejsz
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor

@magento run Unit Tests

Copy link
Contributor

@ihor-sviziev ihor-sviziev left a comment

Choose a reason for hiding this comment

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

Hi @Bartlomiejsz,
Could you fix failing unit tests?

@engcom-Hotel
Copy link
Contributor

Hello @Bartlomiejsz,
I'll check unit tests.

@engcom-Hotel
Copy link
Contributor

@magento run all tests

@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests B2B

3 similar comments
@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests B2B

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

@engcom-Delta
Copy link
Contributor

✔️ QA passed
Manual testing scenario:

  • Create custom theme with layout: 3-columns-double-footer
  • Go to Content->Widgets
  • Click Add Widget
  • Select Type=Catalog Products List and Design Theme=
  • Click Continue
  • Click Storefront Properties->Layout Updates->Add Layout Update
  • Set Display On=All Page
  • Check value $pageLayouts in Magento\Widget\Block\Adminhtml\Widget\Instance\Edit\Chooser\Container

Before:
❌ The function getPageLayouts() only returns the one provided by Magento_Theme
Screenshot from 2021-02-02 11-33-38

After:
✔️ The function getPageLayouts() returns the actual list of page layouts declared by the different modules
Screenshot from 2021-02-02 11-41-04

@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests B2B

2 similar comments
@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests B2B

@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests B2B

@engcom-Hotel
Copy link
Contributor

@magento run all tests

@engcom-Hotel
Copy link
Contributor

@magento run Integration Tests, WebAPI Tests

@engcom-Hotel
Copy link
Contributor

@magento run Integration Tests

@gabrieldagama
Copy link
Contributor

@magento run all tests

1 similar comment
@gabrieldagama
Copy link
Contributor

@magento run all tests

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

1 similar comment
@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

magento-engcom-team pushed a commit that referenced this pull request Mar 7, 2021
…et\Block\Adminhtml\Widget\Instance\Edit\Chooser\Container #31886
@magento-engcom-team magento-engcom-team merged commit 7dd2aac into magento:2.4-develop Mar 7, 2021
@m2-assistant
Copy link

m2-assistant bot commented Mar 7, 2021

Hi @Bartlomiejsz, 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: Widget Partner: Fast White Cat partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Type: Feature/Improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Page layouts are hard-coded in Magento\Widget\Block\Adminhtml\Widget\Instance\Edit\Chooser\Container
6 participants