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

[Backport 2.2] Use correct base path to check if setup folder exists #22369

Conversation

JeroenVanLeusden
Copy link
Member

Original Pull Request

#20182

Description (*)

Current implementation checks the path base/data/web/magento2/pubsetup which is incorrect. It should be /data/web/magento2/pub/setup.

Fixed Issues (if relevant)

  1. Web Setup Wizard not visible in backend magento 2.1.9 #11892
  2. Web Setup Wizard not visible in backend (V.2.1.2) ONGOING #7623

Manual testing scenarios (*)

  1. Install Magento and set doc root is pub/.
  2. Symlink setup folder to pub.
  3. Web Setup Wizard should be visible under System > Web Setup Wizard but it's not.

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 on Travis CI are green)

@m2-assistant
Copy link

m2-assistant bot commented Apr 16, 2019

Hi @JeroenVanLeusden. 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-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.2-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@JeroenVanLeusden
Copy link
Member Author

@orlangur Can you also process this backport PR?

@orlangur
Copy link
Contributor

@JeroenVanLeusden surely, I was already scared by an attempt in your personal fork)

@magento-engcom-team
Copy link
Contributor

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

@ghost
Copy link

ghost commented Apr 16, 2019

@AlexWorking unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

@ghost
Copy link

ghost commented Apr 16, 2019

@AlexWorking unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

@VasylShvorak
Copy link
Contributor

✔️ QA passed

@m2-assistant
Copy link

m2-assistant bot commented Apr 20, 2019

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

@magento-engcom-team magento-engcom-team added this to the Release: 2.2.9 milestone Apr 20, 2019
@JeroenVanLeusden JeroenVanLeusden deleted the 2.2-develop-PR-port-20182 branch April 26, 2019 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants