intexx

Got it, thanks.

I increased max_execution_time to 300 and restarted apache, using this guidance:

https://www.simplified.guide/php/increase-max-execution-time
https://stackoverflow.com/a/11557220

Unfortunately, however, it did not take. The process is still timing out after 120:

[Thu Apr 01 09:47:26.444976 2021] [php:error] [pid 8260:tid 1824] [client ::1:7620] PHP Fatal error:  Uncaught Error: Unknown named parameter $tasks_meta_id in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php:292\nStack trace:\n#0 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#1 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(551): WP_Hook->do_action(Array)\n#2 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\actions\\ActionScheduler_Action.php(22): do_action_ref_array('wpforms_admin_n...', Array)\n#3 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\abstracts\\ActionScheduler_Abstract_QueueRunner.php(65): ActionScheduler_Action->execute()\n#4 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_QueueRunner.php(162): ActionScheduler_Abstract_QueueRunner->process_action(211, 'Async Request')\n#5 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(25, 'Async Request')\n#6 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(292): ActionScheduler_QueueRunner->run('Async Request')\n#7 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#8 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(484): WP_Hook->do_action(Array)\n#9 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_AsyncRequest_QueueRunner.php(52): do_action('action_schedule...', 'Async Request')\n#10 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\lib\\WP_Async_Request.php(156): ActionScheduler_AsyncRequest_QueueRunner->handle()\n#11 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(292): WP_Async_Request->maybe_handle('')\n#12 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#13 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(484): WP_Hook->do_action(Array)\n#14 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-admin\\admin-ajax.php(187): do_action('wp_ajax_as_asyn...')\n#15 {main}\n  thrown in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php on line 292, referer: https://localhost:8080/wordpress/wp-admin/admin-ajax.php?action=as_async_request_queue_runner&nonce=35715369de
[Thu Apr 01 09:48:31.412475 2021] [php:error] [pid 8260:tid 1828] [client ::1:7692] PHP Fatal error:  Uncaught Error: Unknown named parameter $tasks_meta_id in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php:292\nStack trace:\n#0 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#1 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(551): WP_Hook->do_action(Array)\n#2 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\actions\\ActionScheduler_Action.php(22): do_action_ref_array('wpforms_admin_n...', Array)\n#3 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\abstracts\\ActionScheduler_Abstract_QueueRunner.php(65): ActionScheduler_Action->execute()\n#4 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_QueueRunner.php(162): ActionScheduler_Abstract_QueueRunner->process_action(213, 'WP Cron')\n#5 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(25, 'WP Cron')\n#6 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(292): ActionScheduler_QueueRunner->run('WP Cron')\n#7 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#8 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(551): WP_Hook->do_action(Array)\n#9 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-cron.php(138): do_action_ref_array('action_schedule...', Array)\n#10 {main}\n  thrown in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php on line 292, referer: https://localhost:8080/wordpress/wp-cron.php?doing_wp_cron=1617299310.6549110412597656250000
[Thu Apr 01 09:49:43.439320 2021] [php:error] [pid 8260:tid 1832] [client ::1:7648] PHP Fatal error:  Maximum execution time of 120 seconds exceeded in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\Requests\\Transport\\cURL.php on line 463, referer: https://localhost:8080/wordpress/wp-admin/plugins.php
[Thu Apr 01 09:50:06.955711 2021] [php:error] [pid 8260:tid 1832] [client ::1:7766] PHP Fatal error:  Uncaught Error: Unknown named parameter $tasks_meta_id in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php:292\nStack trace:\n#0 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#1 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(551): WP_Hook->do_action(Array)\n#2 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\actions\\ActionScheduler_Action.php(22): do_action_ref_array('wpforms_admin_n...', Array)\n#3 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\abstracts\\ActionScheduler_Abstract_QueueRunner.php(65): ActionScheduler_Action->execute()\n#4 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_QueueRunner.php(162): ActionScheduler_Abstract_QueueRunner->process_action(214, 'WP Cron')\n#5 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-content\\plugins\\wpforms-lite\\vendor\\woocommerce\\action-scheduler\\classes\\ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(25, 'WP Cron')\n#6 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(292): ActionScheduler_QueueRunner->run('WP Cron')\n#7 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#8 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\plugin.php(551): WP_Hook->do_action(Array)\n#9 D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-cron.php(138): do_action_ref_array('action_schedule...', Array)\n#10 {main}\n  thrown in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\class-wp-hook.php on line 292, referer: https://localhost:8080/wordpress/wp-cron.php?doing_wp_cron=1617299406.4644110202789306640625
[Thu Apr 01 09:55:35.894803 2021] [php:error] [pid 8260:tid 1840] [client ::1:7844] PHP Fatal error:  Maximum execution time of 120 seconds exceeded in D:\\<PATH>\\apps\\wordpress\\htdocs\\wp-includes\\Requests\\Transport\\cURL.php on line 463, referer: https://localhost:8080/wordpress/wp-admin/plugins.php

Nevertheless, I suspect two minutes ought to be plenty of time to update a plugin—I’m running an SSD under 16GB of system RAM. The timeout error seems to be a follow-on from the Unknown named parameter error. The former appears to be the real problem. I just don’t know how to decipher it.

Interestingly, one of the previously failing (activated) plugins did update successfully just now. I have no idea why it suddenly worked this time.

Plugin updates work fine on my hosted WP site. It’s only on localhost:8080 that they’re failing.

• This reply was modified 3 years, 11 months ago by intexx.

Got it, thanks.

I’m running PHP v8.0.2.

To clarify, are you suggesting I deactivate the plugin before attempting to update it? I neglected to point out that this is occurring on most plugins regardless of activation/deactivation status.

How would I increase max_execution_time? I found several suggestions on how to do it at runtime, but that approach won’t work for this situation.

I’m not sure which version of PHP I’m using. How would I determine this?

I installed XAMPP/WP in this order:

1. XAMPP v8.0.2
2. XAMPP WordPress Module v5.6.2
3. WordPress v5.7 Update

You could contact your hosts/server admin and ask them to check the PHP error logs

Thank you, but I was under the impression that discussions in this forum are limited to those hosting their own WP instances (which is the case here). Please correct me if I am mistaken.

In any event, I was able to work around this by manually downloading the latest version and uploading it to my WP site.

And while doing so I think I spotted the source of the problem. The manual download came in fits and starts, requiring me to restart it several times. Apparently there’s something amiss at the plugin’s download server.

I think the .ZIP file arrived corrupted or incomplete when I used WP’s plugin update module. In fact, in one of my failed attempts the reported error was a cUrl timeout. That pretty well cinches it, I believe.

The manual update went off without a hitch. Even my settings were preserved, which was nice.

But I’d like to avoid this again for the future. I’m not concerned about having the latest version of this plugin; are you aware of a way to turn off update checks for a given plugin?

Thanks,
Jeff Bowman
Fairbanks, Alaska

Shucky darn, that didn’t help I’m afraid. (But thanks for the lead on Health Check—I like that one.)

For a moment I considered the notion that the dev side dialog might be missing some code for some reason, so I ran a quick file diff between dev and test.

I came up with a few hundred hits, so I guess I won’t be trying that again!

I should probably just be content that it’s only happening in dev (haven’t tried prod yet) and get on with my work. At this point it’s not much more than a nuisance, so I suppose I can ignore it.

Thanks,
Jeff Bowman
Fairbanks, Alaska

• This reply was modified 3 years, 12 months ago by intexx.

@t-p

Pardon me, I didn’t realize that “LightBox” was the name/concept of a plugin. I thought it was the friendly name of the standard WP media selection dialog. I saw the word used somewhere in a related context and made an incorrect assumption.

This is the standard, in-built media selection dialog with the two tabs (Upload Files, Media Library) that we get when we click the ‘Select site icon’ button in Appearance > Customize > Default Settings > Site Identity.

When I choose an image on the Media Library tab and click the Select button at the lower right, the dialog doesn’t close itself like it does in other areas (e.g. setting a page’s featured image). It just stays open indefinitely, never closing and populating the site icon field.

And it only does this on my local installation. My GoDaddy-hosted staging and production sites work fine. This is WP v5.7 (updated manually from v5.6.2) running on XAMPP on my Win10 20H2 machine.

Does that explain it a bit better?

• This reply was modified 3 years, 12 months ago by intexx.
• This reply was modified 3 years, 12 months ago by intexx.