Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
update system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
8 Jan 2007 at 03:20 UTC
Updated:
3 Feb 2008 at 01:43 UTC
Note all the confusion about the message not to run updates more than once at http://drupal.org/node/107616. We need to clarify that message, which is especially confusing to anyone who doesn't open up the hidden part of the page. Seems like we're scaring people unnecessarily.
Is there even any real reason for the warning to be there at all since the system is going to automatically select the right updates to run? A better message might be something along the line of "Don't change these selections unless you have been instructed to do so or you are very knowledgable about Drupal's update system."
Comments
Comment #1
moshe weitzman commentedsounds reasonable, but i don't even understand what changing selections will do. see http://drupal.org/node/105302
Comment #2
karens commentedI posted this over a year ago, but no one seemed interested. Read through the thread I linked to for an idea of how confused people are getting. Not just confused, panicked because of the warning not to run things twice.
I agree that the way this works is not only confusing to newbies but to experienced people, but I was thinking we should at least warn newbies to to leave the selection boxes along and just take the defaults. Then it will be up to module developers to make sure the defaults work right. And that is harder than it may seem, as noted on your link but also http://drupal.org/node/208602.
Then I would put this whole issue on the table for D7 because I'm with you moshe, it really doesn't work the way I expected it would, and neither of us are exactly newbies.
Comment #3
ChrisKennedy commented+1 if anyone wants to do a patch. This has annoyed me for a while but I've been too lazy to do anything about it.
Comment #4
zeta ζ commentedThis appears to have been fixed prior to 6.0-beta1.
Can’t find a similar confusion in 6.0 RC2.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.