Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I use this module for a community site we are currently working on where users can create own blogs and contribute to others. Everything works splendid but I have recently discovered a bug that can be very problematic when we put the site live.
Sometimes (randomly) when editing other vocabularies than the one Ownterm is associated with, Ownterm's checkbox for the vocabulary is reset which means alot of weird things can happen. Would it be possible to add something to the code that prevents this checkbox from loosing its choice?
Thanks for a great module!
Comment | File | Size | Author |
---|---|---|---|
#4 | 621738-ownterm-loses-setting.patch | 948 bytes | coltrane |
Comments
Comment #1
3dloco CreditAttribution: 3dloco commentedHello,
Also, thanks for this great module too! I can confirm this behavior as well, the "enable ownterm" settings on the taxonomy->edit->vocabulary page gets "unchecked" every time I edit any of the other vocabularies.
Thanks,
KH
Comment #2
coltraneThis might be because there can be only one (like Highlander) vocab set for ownterm and the bug is that the old one gets unset. Bah, that'd be bad. I haven't looked at the code in awhile. I'll try to get to this soon.
Comment #3
mattiasj CreditAttribution: mattiasj commentedIt would be great to in some way force Ownterm to protect its vocabulary. At the moment this is (at least what I have found) the best solution for creating a lightweight multi user blogging system. It really works well so i hope this issue can be resolved!
Comment #4
coltraneTry this patch out, it alters the behavior so the variable is only deleted if the checkbox value is 0 and the vocab we are submitting did have ownterm enabled.
Comment #5
3dloco CreditAttribution: 3dloco commented@coltrane: Thanks your patch works! Now ownterm vocab no longer loses its setting when I update other vocabs.
Comment #6
mattiasj CreditAttribution: mattiasj commented@coltrane: Thanks alot, this works great. Can it be commited to a new release?
Comment #7
coltraneI'll try and commit soon and get a new release out.
Comment #8
mattiasj CreditAttribution: mattiasj commentedThanks alot.
Comment #9
coltraneI've committed the patch in #4 and made a development release which will soon appear on http://drupal.org/node/575064/release. I expect to make a 1.1 release next week, so if you would please wait to upgrade your production sites till then.
Comment #10
coltraneFixed in dev release and forthcoming 1.1 release.
Comment #11
mattiasj CreditAttribution: mattiasj commentedGreat job!