Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
update.module
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
4 Oct 2010 at 16:45 UTC
Updated:
8 Apr 2015 at 07:27 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dwwComment #2
damien tournoud commentedThat's a simple fix.
Comment #3
dries commentedCommitted to CVS HEAD. Thanks.
Comment #4
dwwBah. ;) That's what I get for trying to a) deal with this stuff late at night after having a flu for a week, and b) not providing tests. We're now getting duplicate messages on all the Update status and Update manager UI pages, which is pointless, since you're already looking at pages that are either warning you or you're already in the middle of trying to fix it.
Here's a test. This should fail 9 assertions.
Next comment will be the same test with a patch that fixes it.
Comment #5
dwwThis should be all green.
Comment #6
dwwActually, here's a slightly better version of update_init() so we don't incur the cost of calling update_requirements() if we're not actually going to use them. Not sure it's feasible to really test this aspect, so I'm just leaving the same test from #4 to catch the UI bug.
Comment #7
damien tournoud commentedYou can fold the two conditions together, and the second one should be arg(2) === NULL.
Comment #8
dwwGood catch, thanks! You should have set to CNW. ;)
Comment #9
damien tournoud commentedYay.
Comment #10
dwwActually, I think this is a much clearer way to write update_init() that will be less error-prone and easier to maintain in the future.
Comment #11
dries commentedCommitted to CVS HEAD. Thanks.
Comment #12
dwwThanks Dries. Sorry about the extra work with the follow-up patch... Yay for tests. ;)