No plugin update messages displayed in trunk

[pavelevap]

I am using 2.9-rare version and there is no message about new plugin yet even if I know that many plugins were updated. It would be fine to allow updating for trunk version to test plugins with this version and use automatical upgrade...

[dd32]

Example of a plugin thats not working?

Does the Plugin Browser work? (Or throw an error)

Did it work in a previous version? (If so, Which)

[pavelevap]

I use many plugins for testing purposes and no one displays update message (for example Changelogger, I have 1.0.0.1 version, and there were two upgrades 1.0.0.5 and 1.1.0). On all my installations of version 2.8 were these notices displayed, but on my localhost no and there is still oldest version without message. Automatical upgrade of plugin stopped about two weeks ago and no plugin can be automatically upgraded. And the same was with old version Wordpress (there was official 2.7 and I used 2.8-trunk and until 2.8-RC was released, no update message appears).

Plugin Browser and Installation of new plugins works without problem. Only plugin can not be automatically updated because of no message when using trunk from SVN.

[dd32]

I have a feeling this is due to the timeouts on the API requests.

pavelevap: Are you on a slow(er) connection?

All the update API requests time out after 3 seconds.. So that could be it, open wp-includes/update.php and search for 'timeout' => 3, try changing that to 30, if that works its just due to your slow connection.

I'd suggest increasing that timeout to at least 5-8seconds.. its usually run via a cron, so the timeout isnt a huge problem.. Could be increased to a higher value if its a ajax request, and a lower timeout if its being run as a realtime process maybe?

[pavelevap]

Great, thank you! Increasing timeout helped me very much. I use slower connection based on mobile CDMA technology, which is a little slower...

[dd32]

I might knock up a patch which uses a increased timeout on cron-based requests... and that upon a timeout, it doesnt wipe out the update details....

[dd32]

attachment 10439.diff added

• Typo in patch filename, But its for this ticket.

[azaozz]

(In [11826]) Increase timeout on cron-based requests when checking for upgrades, props dd32, fixes #10349

[pavelevap]

Does not work for me. Only sometimes... When I come after some days, there is 6 plugins notified with update messagge. As soon as I update one of them, all others messagges disappear. When I activate any new plugin, messagges appear again, but after update of next plugin, all others disappear once again...

[dd32]

As soon as I update one of them, all others messagges disappear.

Yes, That would be expected, As after you upgrade a plugin, WordPress requires a new API request to be made.. If that times out, Then you will have no update messages visible until the next cron-made request IF the inline cron times out.

When I activate any new plugin, messagges appear again, but after update of next plugin, all others disappear once again...

Because, by that time, The Cron request has completed (Remember, Its probably taking about 10 seconds), in the time between, those on slow connections will have no feedback.

It'd be possible to simply remove the plugin from the update-list, but that'll require some new API on the transients (Specifically, Finding out the age of a transient, so that upgrading a plugin doesnt end up with a forever-extending cache timeout)

[pavelevap]

Thank you very much for clarification. It would be very helpfull to make this work...

[dd32]

You could add this to a plugin or your themes functions.php file in the meantime: (I'd nearly suggest Plugin material)

add_filer('http_request_timeout', '_30sec_http_timeout');
function _30sec_http_timeout($timeout) {
  return ($timeout > 30) ? $timeout : 30; //Return 30 or greater
}

[pavelevap]

I tried to add this to functions.php and also to Hello Dolly plugin, but does not work for me (now does not work also after activating new plugin)...

[dd32]

Sorry a typo:

add_filter('http_request_timeout', '_30sec_http_timeout');
function _30sec_http_timeout($timeout) {
  return ($timeout > 30) ? $timeout : 30; //Return 30 or greater
}

('add_filter' not 'add_filer')

(now does not work also after activating new plugin).

Like i said, Thats just you're slow connection, And due to the availability of the above function, I'm going to reclose this as fixed, Not many installs are hosted on outdated slow links anymore, and the increased timeout for non-realtime requests is all i think you can hope for at the present time.

[pavelevap]

Yes, I noticed typo before, this function does not work for me also with corrected typo... Without this fuction I could see messagges for a while after activating new plugin, but with this function I can not see plugin updates in no case...

[dd32]

this function does not work for me also with corrected typo

Oh 'Duh! I was looking at the defaults.. God i hate the filters in that file, none of them make sense... (ok, some do)

this should:

add_filter('http_request_args', '_30sec_http_timeout');
function _30sec_http_timeout($r) {
  if ( $r['timeout'] < 30 )
    $r['timeout'] = 30;
  return $r;
}

[pavelevap]

Great, it works now, thank you very much. It is great solution which can be used as small standalone plugin for people with slow internet connection.

[hakre]

Cross-Referenced: #11505

[miqrogroove]

*cough* *sneeze* set_time_limit()

*hides*