Closed (fixed)
Project:
Taxonomy Breadcrumb
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Nov 2009 at 11:35 UTC
Updated:
6 Dec 2009 at 20:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
hass commentedBugfix attached.
Only as a side note - module releases in 6.x-1.x need to start with 61xx.
Comment #2
MGN commentedThis is by design. The admin has to select, since there is no obvious default. It will vary from site to site. Its better to leave it as it is, with everything false, so there are no intended consequences.
Perhaps this needs to be better documented.
Comment #3
hass commentedNo. Radio options does not allow keys with false and true. If you need a screenshot...
Comment #4
MGN commentedOk. I see what you mean. I'll roll this in with the next round of updates.
Comment #5
MGN commentedI agree with the changes in taxonomy_breadcrumb.admin.inc (basically changing FALSE to 0 and TRUE to 1), but I am not sure the hook_update is really needed since there are no database changes that need to be made. I haven't noticed any problems without it.
Comment #6
hass commentedI thought this first, too. But nevertheless I've seen in variable table a saved serialized value of
b:0the radio with key 0 wasn't selected. Therefore this is an upgrade path for all who have a serialized boolean value of 0 in their database. I believe this have something to do with form API, but you cannot really see the issue if you have a boolean of 1 in the DB. Why - I don't know - but this upgrade hook brings all users to the same values with integer 1 or 0 and should therefore more painless than everything else.It has been tested in several ways :-).
Comment #7
hass commentedAside - I missed one line in the .module file - FALSE need to become 0 here, too.
Comment #8
hass commentedUpdated patch attached.
Comment #9
MGN commentedThanks. Committed to 6.x-1.x-dev.
Comment #10
hass commentedthx