Drupal security update forcing update status "error message" on admin pages
doc2@drupalfr.org - January 31, 2008 - 16:46
| Project: | Update Status |
| Version: | 5.x-2.1 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | dww |
| Status: | closed |
Description
Hello, and firstly thank you for this great module!
In version 2.0, when ignoring a drupal core update, no status update "error message" showed up. Now with version 2.1, it does: "There is a security update available for your version of Drupal. To ensure the security of your server(...). It is a problem for me, as I use it on a Beta "public" intranet site.
I have no time to update drupal core on the beta version of my site because I'm working on the up-to-date stable version! I wouldn't like to downgrade my Beta to version 2.0, as you introduce many critical bug fixes is th 2.1 release... Anything to do then?
Many thanks, greetings
Arsène
#1
I don't understand what you're talking about. You mean you configured update_status to ignore core releases in general? Or you configured it to ignore a specific core release? Or something else entirely? Please clarify. Screenshots of your update_status settings page and the error message you're seeing would probably be helpful.
#2
Oh, I see what you're talking about now. Yeah, I broke the ability to ignore projects via the settings if the project has security updates available, or has been unpublished, etc. This should fix it. However, I'm not *sure* it's a good idea to ever let people ignore these things. ;) I'd like to think about that a little more before I commit this. Input from merlinofchaos would be welcome.
#3
IMHO, As long as those people are admins, they should have the choice.
Indeed, ignoring is already a kind of option set to OFF by default, with the "parameters" tab behind the main page. I suggest that a simple alert about the possible issues of the ignoring option be enlighted on the parameters page.
Other suggestions welcome.
Thanks for the patch. However not tested yet. I hope you kept the option!
#4
Briefly discussed this with merlinofchaos in IRC. As expected, he's in favor of fixing this. So, I just committed the patch to DRUPAL-5--2. 5.x-2.2 should be out sometime today.
#5
Commited! Installed!! Works great!!! Hi five!!!!
#6
Automatically closed -- issue fixed for two weeks with no activity.