Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
update.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Mar 2011 at 13:27 UTC
Updated:
29 Jul 2014 at 19:25 UTC
The 'update_max_fetch_time' variable controls the number of seconds that update.module will spend polling drupal.org for project updates to display in the Update Manager (admin/reports/updates), and also affects the number of projects displayed via drush (#1002658: Drush does not correctly handle D7 project status queries). Unfortunately there's no way of modifying this variable via the UI, so a simple field added to admin/reports/updates/settings would greatly help.
Comments
Comment #1
damienmckennaIs this a bug report as a core variable doesn't have a way to modify it, or a feature request?
Comment #2
bfroehle commentedI would say this is a feature request. Core has numerous variables for which no settings pane is provided.
Comment #3
cyberwolf commentedSubscribing.
Comment #4
jeffschulerI got here via #1002658: Drush does not correctly handle D7 project status queries too.
Changing the variable (via
drush vset update_max_fetch_time 60) solved the problem for me, but it took some time to figure out why the updating process was acting inconsistently and differently than it used to.Since this affects the updating process so profoundly, I think it deserves more obvious configurability and documentation in the UI.
Comment #5
dwwI'm not sure we need a visible knob for this. If you use the UI, Update manager drains this queue completely via a batch. The real problem is that I broke some functions drush was relying on via #597484: Use the Queue API to fetch available update data and I think there are better ways to fix that than to tell people they should up this knob manually on their sites (as I just explained over at #1002658: Drush does not correctly handle D7 project status queries). So, -1 to more configuration UI for this, but I'm open to discussing it before I outright "won't fix" this. ;)
Comment #6
jeffschulerIt has seemed to me that this problem hasn't been limited to Drush -- that the Updates page now often doesn't have up-to-date info on all modules, and I have to click "Check manually" a lot more now than I used to, (pre-D7, pre-git-migration.)
I'm willing to let go of this til the Drush fix goes through, though, if you think that should get things back to good.
Comment #7
bfroehle commentedThis is was created to solve the same problem as #952394: "No available releases found" - fetching update information exceeds timeout. In particular, #952394-79: "No available releases found" - fetching update information exceeds timeout discusses adding UI elements for this variable which later posts argue is too techy.