Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Strange problem: If you're using Content Taxonomy with the Options Widgets module and have for example two Taxonomy terms named "term 1" and "term 2" as checkboxes, one of them has to remain checked or the change isn't recorded.
You can check "term 1" or "term 2" and it works, you can check "term 1" and "term 2" and it works, but if you uncheck both "term 1" and "term 2" nothing happens.
Driven forces one of the checkboxes to always be selected. The terms can be unchecked by editing the node the old fashioned way, so the problem is definitely with Driven.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 2011-04-02_873502-4.patch | 2.1 KB | arhak |
| #3 | uncheck error.png | 5.76 KB | andystox |
| #2 | content_taxonomy_driven_checkboxes.png | 3.72 KB | jthomasbailey |
| #2 | content_taxonomy_basic_settings.png | 38.65 KB | jthomasbailey |
| #2 | content_taxonomy_options.png | 71.56 KB | jthomasbailey |
Comments
Comment #1
arhak commentedcould you please provide detailed configuration of your content_taxonomy field?
Comment #2
jthomasbailey commentedHere you go.
Comment #3
andystox commentedI am having the same issue.
I'm using content taxonomy to generate a checklist of taxonomy terms and I'm using the editablefields module to allow them to be edited in place.
It all works fine unless I have only one item checked, when I try to uncheck that item I get an error warning: Cannot use a scalar value as an array.
It looks like it's expecting the object to be an array but it's not.
Have you had any luck with this issue?
Comment #4
arhak commentedindeed,
thanks for your report, it is more specific,
I have a clue whether the problem might lie,
regretfully, I don't have the time to dig into it
Comment #5
arhak commentedguys, I need you to do some test that might seem unrelated, but it is required to avoid regressions
this bug was introduced while attempting to cover another different case:
- content_taxonomy with autocomplete widget
- Deny any new terms: checked
- attempting to introduce new tags leads to a validation error
- therefore no diff should be shown
attached patch aims current issue and also attempts to preserve case mentioned above
Comment #6
arhak commentedComment #7
arhak commented@#3
BTW never got to reproduce the "Cannot use a scalar value as an array" error
could you please provide the full error message (to see if it is displaying a filename & line number)
PS: proposed patch addressed OP, not sure what can be causing error @#3, that one would require more details and most likely its own separated issue