-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add an option to install and set up all canonical extensions #44
Comments
Thanks for creating this issue, @Aljullu. While this is a great idea, I'm afraid, it's only possible to install extensions that are available on w.org. Paid extensions, that are only available via the Woo Marketplace, cannot be installed via WP CLI. From your comment in https://wp.me/pf59Ax-yA#comment-350, I understood that this specific bug could have been discovered when AutomateWoo had been installed. Unfortunately, AutomateWoo is one of the paid extensions which cannot be installed via WP CLI. With that said, can you list free extensions that should be included into this custom WP CLI command? |
Recently, we had a couple of bugs that were reproducible in WooExpress but not in the local set-ups we use for development: woocommerce/woocommerce#43269 (pf59Ax-wM-p2) and woocommerce/woocommerce#43177 (pf59Ax-yA-p2). That's because the issues were only reproducible when certain extensions were installed.
It would be great if
woo-test-environment
had an option to install and set up all canonical extensions. This would make it easy to test our PRs in an environment more similar to WooExpress and catch issues like those ones.The text was updated successfully, but these errors were encountered: