Need to start a separate issue, because the other thread needs to stay as D5, but it would be great to see a D6 patch for the feature here:
http://drupal.org/node/172797

I will probably end up doing it, if I get the chance over the next few weeks. =)

(Please don't mark this as duplicate - it isn't duplicate, because D6 won't be considered in the other thread, so I've raised a separate issue to get this in the queue!)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ngaur’s picture

+1

Can I give it more than 1 ? Without taxonomy I can't use this module, and it's otherwise just the thing I need.

obrigado’s picture

Subscribing... this functionality would be great.

greg.harvey’s picture

See #172797: Modify Taxomonmy on added and edited items?, comment #10 for a quick solution. Works for me. Will make a patch.

greg.harvey’s picture

Version: 6.x-1.x-dev » 6.x-1.0-beta1
Status: Active » Needs review
FileSize
714 bytes

Patch of the above suggestion attached. It's actually against beta1.

Aren Cambre’s picture

Title: Modify Taxomonmy on added and edited items? (Drupal 6) » Doesn't allow taxonomy edits
Category: feature » bug

I think this is actually a bug fix.

dirksonii’s picture

This patch unfortunately does nothing on my (fresh yesterday) install.

greg.harvey’s picture

Odd. It works just fine for me. See screens attached of UI and View settings. Are you sure you're not misunderstanding how it works/what it's supposed to do?

dirksonii’s picture

Nope, I know what it's supposed to do. After a bit of fiddling with patch supplied, it looks like the if statement around the "display as taxonomy" bits never returns true. (When I set it to always return true, it works, but then I can't see the CCK fields, which are utterly required in my application) I'm using tagging, not the usual taxonomy, perhaps that's the problem?

greg.harvey’s picture

Status: Needs review » Needs work

Could be - haven't tried it with tagging. Setting to "needs work".

cridenour’s picture

@3: Works perfectly for me and saved me the trouble of a module development cycle just to bulk edit.

Thanks for the link.

greg.harvey’s picture

@cridenour, did you try #3 with a vocab set to free tagging?

cridenour’s picture

@greg.harvey

Sorry for slow reply. I haven't had the chance to test this with free tagging. It was on a semi-production level site so I was merely looking to make my bulk-editing life much easier. If I get the chance, I'll test on my dev box.

pimousse98’s picture

Hi, I tested the patch and:
* it shows taxonomy as drop down, for my non-tag, unique term vocabulary.
* however in my table form it displays the standard title and instructions for the vocabulary, in each cell (so in addition to the column name I get the voc name and instructions around the drop down), which is quite a problem.
I just tried with a tagging vocab and the results are the same, except the output is not really a table anymore (for each row, I get a bunch of giant autocomplete fields on top of each other in the first cell.). Is there a way to remove the labels and make the layout a little nicer for multiple taxonomy fields?
Thanks

scoorch’s picture

To use taxonomy under editview you can also use the Content Taxonomy Module to store taxonomony data as cck field. These fields can be edited within viewedit

greg.harvey’s picture

Nice tip, scoorch! =)

The patch above seems to work fine with Hierarchical Select, much to my surprise, so that's worth knowing.

Problem is, development of this module for Drupal 6 doesn't seem to be happening (last commit in May last year), I've got this feature working as far as I need it to and I have no more time to devote to it, so someone else will need to take this patch and help me expand on it. Even then, it's not clear if it will be committed in any hurry...

webchick’s picture

Didn't fix my issue (unrelated, it seems... I'm seeing "Authored by" instead of "Terms" in the view...), but here's a patch that applies cleanly to 6.x-1.x anyway. :)

greg.harvey’s picture

Version: 6.x-1.0-beta1 » 6.x-1.x-dev
Status: Needs work » Needs review

Thanks webchick! Changing version to match and status to "needs review" as more people have said it works than haven't. Some conclusive testing needed against the core Taxonomy features, I guess.

Frodo Looijaard’s picture

Assigned: Unassigned » Frodo Looijaard
Status: Needs review » Fixed

Taxonomies should now work. The fix is basically webchick's patch with some enhancements. Thanks for reporting and sending patches!

westis’s picture

Status: Fixed » Active

I can't get taxonomy terms working. That is, there is nothing editable in those fields. Is it supposed to work with free-form tags too? I'm using the latest dev version.

In fact, when I add "Taxonomy: All terms" as a field, I get this error message: warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /public_html/sites/all/modules/contribute/editview/theme/editview.theme.inc on line 116.

MBroberg’s picture

I am also using the latest dev and I have both "Term" and "All Terms" attached to the view. Neither is showing up in the edit form. I did not see any error message.

MBroberg’s picture

Correction: I am seeing "All Terms" but not "Terms". I have "All Terms" limited to a single vocabulary which is a tagging vocab. I have an autocomplete box showing in each record.
I also have "Active Tags" module enabled. I am getting suggested tags in the "add new" form but not in the rest of the records.

MBroberg’s picture

Additional Note: After activating "Taxonomy Super Select" for the content type, I am now seeing checkboxes for popular terms on both new and existing records.

davidneedham’s picture

FWIW, it doesn't seem like this patch was rolled into the latest 6.x-1.x-dev, or the latest recommended release (6.x-1.0-beta3). Unfortunately the folder structure has changed significantly and there is no longer a editview.theme.inc, and the word "taxonomy" can't even be found in the remaining files. So I'm not sure where that leaves this, except that it's defunct and patching needs to start over from scratch. :-(