Content Taxonomy fields gone

castawaybcn - September 7, 2009 - 15:05
Project:Content Taxonomy
Version:6.x-1.0-rc2
Component:Code
Category:support request
Priority:critical
Assigned:Unassigned
Status:closed
Description

I have a content type which includes some cck taxonomy fields and I display it through views. After upgrading to 6.x-1.0-rc2 my previously working view complained about an illegal choice, and when I looked in the logs there were several entries like this:

Illegal choice 45 in field_mycustomfield_value element.
Illegal choice 46 in field_mycustomfield_value element.

The only errors I got where from terms 45 and 46, although many others where not showing either.

Then I found out that when I tried to generate a node of that content type, in some of the cck fields the options (regardless of the selection method used) were no longer available.

The errors posted above corresponded to the first two terms (out of five) of the first cck taxonomy field (out of 3).
The second cck taxonomy field had the same problem, that is, no options available, but returned no visible errors.
The third cck taxonomy field however was displayed correctly.

Reverting tot 6.x-1.0-rc1 fixed the issue.

Please do let men know if I can provide any further information about this issue (and which).

Thanks for such a useful module, I couldn't work without it.

#1

mh86 - September 7, 2009 - 18:56

Hi!

This is a strange bug, would be interesting if someone else is facing the problems after upgrading from rc1 to rc2.
There have not been that much changes since rc1, so at the moment I have no idea.

Can you tell me, which widgets exactly with which settings are you using?

#2

castawaybcn - September 8, 2009 - 08:55

Common settings for the 3 fields:
- Required.
- Has default value
- No custom php code is applied
- Child terms are indented with ' - ' signs
- Only 1 possible value
- Values not added to the core taxonomy system

FIELD 1 (no options available using rc2)
- widtget: select list (tried changing it to checkboxes/radios but made no difference)
- other settings: has default value, no php code, child terms are indented with ' - ' signs, only 1 possible value, values not added to the core taxonomy system

FIELD 2 (no options available using rc2)
- widtget: select list

FIELD 3 (this one did show the options using rc2)
- widtget: tree

Just so that you have an idea of what I am dealing with, here's a screenshot of the view I am using. Essentially it's a tasklist with an exposed "status" filter. The cck taxonomy terms used correspond to Priority(1), Status(2) and "Assigned to" (3)

Do let me know if you need more information. Be aware though that I am experiencing this issue on a live site, so the number of tests I can do is limited.

AttachmentSize
cc_tax_view.jpg 31.99 KB

#3

mh86 - September 9, 2009 - 08:15

Hi!

Thanks for the detailed listing. It seems like, the problem lies in the function content_taxonomy_allowed_values($field), this function returns the option arrays for select list / checkboxes / radio buttons. The tree widget has it's own mechanism.

In RC2, I made changes to this function, but they where only related to optgroups, so maybe you have selected a term under "Parent term for OptGroups in select fields: " ?

#4

castawaybcn - September 9, 2009 - 09:39

yep,
but to be perfectly honest I just have no idea if I need it or not... Perhaps you may provide some light here.
should I disable it?

#5

mh86 - September 9, 2009 - 09:54
Category:bug report» support request
Status:active» fixed

I don't think you need opt-groups (= select list containing not-selectable grouping terms). In RC2, opt-groups are generated as they should be (at least I think so ;) ). This option might be a bit confusing, and your taxonomy needs a special structure to support it.
If you disable this option and upgrade from RC1 to RC2 I'm pretty sure your fields are going to work as expected :)

#6

castawaybcn - September 10, 2009 - 12:04

Followed your instructions and updated to RC2 just now, everything working as expected.

Thanks!!

#7

System Message - September 24, 2009 - 12:10
Status:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.

 
 

Drupal is a registered trademark of Dries Buytaert.