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

Error in vendor/magento/module-shipping/Model/Config/Source/Allmethod… #25315

Merged
merged 3 commits into from
Dec 29, 2019

Conversation

mrodespin
Copy link
Contributor

Description (*)

If a module has a selectable configuration using the source app/code/Magento/Shipping/Model/Config/Source/Allmethods.php and one shipping method has the allowed shipping methods to null admin page won't render properly (Blank page)

Fixed Issues (if relevant)

  1. Error in vendor/magento/module-shipping/Model/Config/Source/Allmethods.php - public function toOptionArray #13136: Error in vendor/magento/module-shipping/Model/Config/Source/Allmethods.php - public function toOptionArray

Manual testing scenarios (*)

  1. Made a composer require of the module described on the task (magmodules/magento2-channable)
  2. Edited the configuration value carriers/usps/allowed_methods to NULL on core_config_data.
  3. Open the admin configuration of channable module.
  4. Checked that the configuration page throws and error and no content is rendered.
  5. Reviewed how usps module returns the allowed methods on this file app/code/Magento/Usps/Model/Carrier.php
  6. Modified the file app/code/Magento/Shipping/Model/Config/Source/Allmethods.php for control this error with all allowedmethods functions.

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)

@m2-assistant
Copy link

m2-assistant bot commented Oct 27, 2019

Hi @mrodespin. 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.3-develop instance - deploy vanilla Magento instance

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

@osrecio osrecio added Partner: Interactiv4 Pull Request is created by partner Interactiv4 partners-contribution Pull Request is created by Magento Partner labels Oct 27, 2019
@kalpmehta
Copy link
Contributor

@mrodespin Can you please cover the changes with tests? Thanks

@kalpmehta kalpmehta self-assigned this Oct 28, 2019
@sidolov sidolov changed the base branch from 2.3-develop to 2.4-develop December 5, 2019 17:17
@kalpmehta kalpmehta added the Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests label Dec 10, 2019
@magento-engcom-team
Copy link
Contributor

Hi @kalpmehta, thank you for the review.
ENGCOM-6436 has been created to process this Pull Request

@engcom-Delta
Copy link
Contributor

✔️ QA passed

@engcom-Golf engcom-Golf added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests and removed Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests labels Dec 19, 2019
@m2-assistant
Copy link

m2-assistant bot commented Dec 29, 2019

Hi @mrodespin, 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.

@sdzhepa sdzhepa mentioned this pull request May 9, 2022
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 Award: bug fix Component: Shipping Partner: Interactiv4 Pull Request is created by partner Interactiv4 partners-contribution Pull Request is created by Magento Partner Progress: accept Release Line: 2.4 Squashtoberfest 2019
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants