I find this module (http://drupal.org/project/content_taxonomy) extremely useful. Would there be any way to add support for it in your module?

ta

Comments

cyu’s picture

cyu commented

I don't have any motivation to code that up, but I would welcome a patch that added this support.

Matto’s picture

Matto commented

+ $0.02 - The additional functionality suggested here by castawaybcn would be very useful for me too. But I don't have the skills to help with a patch.

summit’s picture

summit commented

Subscribing, would be great to have cck_content_taxonomy support also!
greetings, Martijn

malberts’s picture

malberts commented

I found a way that *seems* to be working.

Look in option_trim.module and look for lines that look like:

$valid_widgets['nodereference'] = array('nodereference_select');
$valid_widgets['userreference'] = array('userreference_select');
$valid_widgets['rolereference'] = array('rolereference_select');
$valid_widgets['text'] = array('optionwidgets_select');
$valid_widgets['number_integer'] = array('optionwidgets_select');
$valid_widgets['number_decimal'] = array('optionwidgets_select');
$valid_widgets['number_float'] = array('optionwidgets_select');

and then add

$valid_widgets['content_taxonomy'] = array('content_taxonomy_select');

after that.

I'm not going to make a patch for this right now. It seems to be picking up the values in the Content Taxonomy Select list. I haven't tested it any further than making it trim some values in a node and then saving the node/opening it and it looked fine. The added line will only work for the CT Select list widget. I haven't tried to make the other widgets work.

castawaybcn’s picture

castawaybcn commented

Although I have not tested it thoroughly the trick proposed by malberts seems to be working just fine.
Thanks so much!!

rburgundy’s picture

rburgundy commented

+1 subscribing

rdeboer’s picture

rdeboer
Location Melbourne
commented

Also very much after this feature.
Tried the patch by malberts in #4 of this thread. But doesn't work.
That patch dates back to before the current 6.x-2.2 release, which is what I'm using.

cyu’s picture

cyu commented
Status: Active » Fixed

I never got around to looking at this, but was assuming that taxonomy field worked like most of the other reference fields in having elements stored in a way that requires a special case. That was not the case.

So 3.5 years later, I've committed that one line patch. http://drupalcode.org/project/option_trim.git/commitdiff/17f85db

Status: Fixed » Closed (fixed)

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