Yoast / Yoast/plugin-development-docker
Console spam on woocommerce-wordpress's first start
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Until now I only ran the default ./start.sh on this laptop.
Today I ran ./start.sh woocommerce-wordpress and while installing it showed a lot of output.
For example:
[22-Oct-2020 11:27:42 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wc/v3/brands</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/html/wp-includes/functions.php on line 5225
[22-Oct-2020 11:27:42 UTC] PHP Stack trace:
[22-Oct-2020 11:27:42 UTC] PHP 1. {main}() /usr/local/bin/wp:0
[22-Oct-2020 11:27:42 UTC] PHP 2. include() /usr/local/bin/wp:4
[22-Oct-2020 11:27:42 UTC] PHP 3. include() phar:///usr/local/bin/wp/php/boot-phar.php:11
[22-Oct-2020 11:27:42 UTC] PHP 4. WP_CLI\bootstrap() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[22-Oct-2020 11:27:42 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[22-Oct-2020 11:27:42 UTC] PHP 6. WP_CLI\Runner->start() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[22-Oct-2020 11:27:42 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[22-Oct-2020 11:27:42 UTC] PHP 8. WP_CLI::do_hook() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1263
[22-Oct-2020 11:27:42 UTC] PHP 9. WC_CLI_Runner::after_wp_load() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/class-wp-cli.php:304
[22-Oct-2020 11:27:42 UTC] PHP 10. do_action() /var/www/html/wp-content/plugins/woocommerce/includes/cli/class-wc-cli-runner.php:59
[22-Oct-2020 11:27:42 UTC] PHP 11. WP_Hook->do_action() /var/www/html/wp-includes/plugin.php:478
[22-Oct-2020 11:27:42 UTC] PHP 12. WP_Hook->apply_filters() /var/www/html/wp-includes/class-wp-hook.php:311
[22-Oct-2020 11:27:42 UTC] PHP 13. Perfect_Woocommerce_Brands\PWB_API_Support->register_endpoints() /var/www/html/wp-includes/class-wp-hook.php:287
[22-Oct-2020 11:27:42 UTC] PHP 14. register_rest_route() /var/www/html/wp-content/plugins/perfect-woocommerce-brands/classes/class-pwb-api-support.php:38
[22-Oct-2020 11:27:42 UTC] PHP 15. _doing_it_wrong() /var/www/html/wp-includes/rest-api.php:103
[22-Oct-2020 11:27:42 UTC] PHP 16. trigger_error() /var/www/html/wp-includes/functions.php:5225
Since I have my history capped I'm not sure what it was doing to cause these, but after those it continued with attachment generation, product category generation, etc. (no more spam).
Good to note that it seems to install fine. It just obscures any potential information on the actual installation process.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running ./start.sh woocommerce-wordpress and inspect the installation output around attachment and product category generation. The report points to /var/www/html/wp-content/plugins/perfect-woocommerce-brands/classes/class-pwb-api-support.php:38 and the WordPress REST route warning; trace how that output reaches the console. Done means installation progress is readable without the repeated notices obscuring it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php, shell, wordpress
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100