Closed (fixed)
Project:
Own Term
Version:
6.x-1.0
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Nov 2009 at 07:16 UTC
Updated:
3 Jan 2014 at 00:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
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 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 commented@coltrane: Thanks your patch works! Now ownterm vocab no longer loses its setting when I update other vocabs.
Comment #6
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 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 commentedGreat job!