When no vocabulary is selected for a given content type, after submitting, they are all selected. It has been observed on one installation detailed at the end.

I want to have content type with and without associated vocabulary. Those with associated vocabulary work fine. But, for those without association, if I unselect all boxes, after submitting it is as if they had all been selected. I used for a long time a workaround using a dummy vocabulary, but it makes other problems in the workflow a the site. I have not checked if direct selection within the db would be possible.

MySQL 5.0.51a

PHP 5.2.0-8+etch16

jQuery UI 1.6

CommentFileSizeAuthor
#16 Create Page | localhost.jpg14.9 KBipwa
#16 NAT | localhost.jpg15.62 KBipwa
#11 2010-02-25wBetterSelect001.png63.63 KBnardberjean
#11 2010-02-25wBetterSelect002.png57.96 KBnardberjean
#9 2010-02-25w020.png72.87 KBnardberjean
#7 primavera_nat_3.png21.14 KBnardberjean
#2 Capture-NAT_before.png62.73 KBnardberjean
#2 Capture-NAT_after.png71.31 KBnardberjean

Comments

anantagati’s picture

anantagati commented
Status: Active » Postponed (maintainer needs more info)

Can you please send screenshot of you NAT setting page?

nardberjean’s picture

nardberjean commented
Status: Active » Postponed (maintainer needs more info)
StatusFileSize
new Capture-NAT_after.png71.31 KB
new Capture-NAT_before.png62.73 KB

Some screenshots

The first one is the configuration as it is working now, with the illustrated content type having a dummy vocabulary 'Default' associated with. I unchecked the 'Default' vocabulary, so that no vocabulary was associated with the document type and submitted. The resulting is the second screenshot, where all possible vocabulary are associated with the document type.

nardberjean’s picture

nardberjean commented
Status: Postponed (maintainer needs more info) » Active
anantagati’s picture

anantagati commented

What version of NAT module are you using? Are you sure that it is latest 6.x-1.x-dev?

nardberjean’s picture

nardberjean commented
Status: Postponed (maintainer needs more info) » Active

OOps, there have been a directory issue it was Node Auto Term [NAT] 6.x-1.x-dev (2009-mars-01) with a patch can be seen on #2 screenshots to allow to have parent term, which is totally needed in that website.

I replaced it by Node Auto Term [NAT] 6.x-1.x-dev (2010-févr.-18) without any patch.

Testing again.

The bug remains exactly as described previously.

anantagati’s picture

anantagati commented
Status: Active » Postponed (maintainer needs more info)

I cannot reproduce that bug. So may be a problem with your installation. Can you please test NAT on fresh Drupal install?

nardberjean’s picture

nardberjean commented
Status: Postponed (maintainer needs more info) » Active
StatusFileSize
new primavera_nat_3.png21.14 KB

I reproduced a similar bug on a site with a fresh database, but also a lot of modules. I created one vocabulary and the nat setting page was fine. I created two other vocabulary and then I went to nat settings, all document types which had no vocabulary associated had, without manual intervention, 3 of them selected !

I join a copy of screen.

anantagati’s picture

anantagati commented

When I install fresh Drupal and NAT, on setting page there are no checkboxes for vocabularies, I have there select widget.
So maybe some module interfering with settings.

Try to install NAT on fresh Drupal with just core modules and check if it works good.

nardberjean’s picture

nardberjean commented
StatusFileSize
new 2010-02-25w020.png72.87 KB

With a fresh database and few modules it woks perfectly, but I observ and do not understand why the selection widget for the vocabularies is selection list instead of selection boxes?

Attached is screenshot.

anantagati’s picture

anantagati commented
Status: Active » Fixed

There are no check-boxes because it is made as select.

So it seems it is not a bug. Closing issue. You can enable different modules and find which module is making problems.

nardberjean’s picture

nardberjean commented
Status: Fixed » Active
StatusFileSize
new 2010-02-25wBetterSelect002.png57.96 KB
new 2010-02-25wBetterSelect001.png63.63 KB

Looks like an incompatibility with the Better Select module

http://drupal.org/project/betterselect

I installed Better Select and NAT settings page get transformed, the selection lists were replaced by selection boxes, which appeared unchecked as you can see on screenshot 1.

Without checking any boxes I submitted the page and the updated version of it showed all vocabularies selected, as shown on screenshot 2.

Maybe this issue should be changed name and project, but incompatibility could be written in documentation, as long as issue is not solved, because multimodule incompatibilites are longer to find.

anantagati’s picture

anantagati commented
Title: admin/settings/nat : impossible to select no vocabulary » Better Select not compatible with Node Auto Term (NAT) module
Project: Node Auto Term [NAT] » Better Select
Priority: Critical » Normal
nardberjean’s picture

nardberjean commented
Version: 6.x-1.x-dev » 6.x-1.0-beta2
Priority: Normal » Critical

I used Better Select 6.x-1.0-beta2 no idea about dev version.

Thanks for your help anantagati.

nally’s picture

nally commented

subscribe

ipwa’s picture

ipwa commented

I can confirm the bug in #11.

I investigated a little further on why this happens. The multi select element on NAT breaks with BetterSelect because it doesn't have a 'None' option. If the NAT module would provide a 'None' option like most other Drupal multi select elments do, this would not be an issue.

node-form

nat-settings

ipwa’s picture

ipwa commented
StatusFileSize
new NAT | localhost.jpg15.62 KB
new Create Page | localhost.jpg14.9 KB
ipwa’s picture

ipwa commented

See: Issue #1407566: Better Select does not work on select elements without "-None-"/"-Select-" options