I have heavily modified the code for this module to the point that I don't think a patch makes sense. i.e. few lines are left unchanged/in place.

What I have done is add the checkbox/fieldset display of the taxonomy_super_select module and added hierarchical freetagging. This means that a user can collapse/expand each branch, add leaf terms, create new branches, and so on. Leaves and branches are both checkable.

Since mine is a derivative work and the community frowns on creating 'me-too' projects, I'm wondering if you would like to create a new branch, patch the existing one, or have me start a new project. I'll need an answer soon. Thanks.

I'm not posting a patch or a file at this time since a) I didn't make a patch, and b) I've renamed the file and created a new .info file.

Comments

robertdouglass’s picture

wow! Let's see the code. If it preserves the intent of the original and builds upon it, I'd love to add it into this project.

robertdouglass’s picture

you can zip it up and attach it here ... no need to patch.

rconstantine’s picture

StatusFileSize
new8.89 KB

Here's the zip. One note. In further testing, it seems the case where the taxonomy is set to NOT have multiple terms, which corresponds to radio/fieldsets in this module does not work. It LOOKS like it works, but upon submitting the page, Apache takes a dump. My logs tell me nothing as to why.

The checkbox stuff works fine.

Recommended settings: At the taxonomy level: check 'Multiple select' and 'Free tagging'. At the cck_field level: check 'Display parent terms as selectable form items'.

Unchecking 'Multiple select' is what puts this module into radio button mode. 'Display parent terms as selectable form items' makes it so that one can select a branch (fieldset) term. This is important because with the way I setup free tagging, users can turn leaf terms into branches and other users may have selected that term before. One thing I didn't add is the option to make free tagged terms NOT added to the cck field table. I have operated on the assumption that if a user adds a term, they would also 'check' the term. So at submission, if a term is added, it is added to the content_field_blah_blah table just like checked terms are. The use case where this is a detriment is if the site admin just wants to use this as a super-fast way to construct a vocabulary. One last note - I didn't even try to get comma separated lists of terms to work in free tagging. Oh, and it could all possibly be prettier.

So check it out. Any help with getting the radio buttons to work would be great. I'll write up a README if you choose to accept this module. I also heavily commented the code since I like to use PhpDocumentor.

Remove the .patch extension from the zip.

rconstantine’s picture

Actually, feel free to toggle the free tagging to see how things look both ways. That shouldn't be a problem.

robertdouglass’s picture

thanks. It might be some days before I can look at it, but I'm looking forward to having the chance.

rconstantine’s picture

I'm just pestering you to see if you've had a chance to look at it/test it yet. I want to make another addition, but sort-of want to make sure you don't find any other glaring mistakes before I do.

Basically, I want to add an optional drop down next to each and every term. That drop down will be populated with ratings or levels, the text of which would be defined by the admin so that it could be used for different purposes. My original use for this module (before the drop down) is so that users can populate and indicate their interests. Clearly that is a check/uncheck situation. Then I thought about listing skills and abilities with a self evaluation of skill-level. So that's what the drop down would add, the ability to rate some kind of term. I'm sure this could be used for such things as job-finding sites (maybe temp agencies?), dating sites or whatever. I'm sure I'm not even considering a bunch of other possibilities.

So if you get a chance to look at this soon (and maybe commit an official/dev release?), I'll get to adding this.

Thanks.

rconstantine’s picture

StatusFileSize
new0 bytes

Well, I added my changes anyway. Here's what's new:

In addition to having a hierarchical presentation of a vocabulary with hierarchical free tagging, now the admin has the option to place a ratings selector next to each term. If this option is used, the admin can select the title of the selector (or use the field for instruction) and can list the options. I'll be using this as a 'skills' vocabulary in a nodeprofile and users will add skills and rate their abilities. This could also be used for other things as well. I could imagine that an admin might use taxonomy terms as urls to recipes and have the selector list preparation times. Whatever.

The only bummer is that I didn't spend the time to come up with a nice theme function. I took the shortcut of putting the checkbox and selector in a fieldset side-by-side, so everything is even more fluffed than the checkboxes alone. I think someone over at taxonomy_super_select worked out a css file or theme or something to slim down the vertical space taken by the checkboxes. I haven't checked it out yet.

I also added diff module support to this and my other cck modules.

rconstantine’s picture

Status: Active » Needs review

I forgot to mention that this latest version adds a column to the cck-controlled table, so there's an .install file now that will update existing installations.

robertdouglass’s picture

Thanks. I've not forgotten... but I'm very very snowed under at the moment.

michelle’s picture

I hate doing this but my bookmarks are such a mess... I'll be able to track this better in my tracker. Subscribing. :)

This sounds like a really awesome rewrite and I want to check it out when I can.

Michelle

rconstantine’s picture

StatusFileSize
new43.5 KB

It seems something didn't work with the last upload as there are 0 bytes in it.

rconstantine’s picture

I forgot to mention to remove the .patch extension from the tar.

robertdouglass’s picture

Status: Needs review » Closed (won't fix)

I don't really like the interface for this. From what I can tell, there are a lot of changes just to change the interface. It seems like a better way to do this would be within the taxonomy module, since that is where the select is themed. That would also affect this module, yet keep the concerns separate.

rconstantine’s picture

I'm not sure what you mean when you say you don't like the interface. That's kind of vague. Of course, I respect that you have a different opinion. There's no right or wrong here. I happen to like the interface a lot, and as I don't think that core modules should be messed with, and as I don't want to wait for Drupal 6 hoping that the taxonomy module gets the upgrades I'd like it to have, I think this is a good solution that places a visual emphasis on the taxonomy layout. On top of that, it addresses a huge shortcoming that free tagging has in Drupal; that being it isn't hierarchical.

So thanks for looking at my changes. I'll move them to their own project.

Cheers.

michelle’s picture

Pity it's been won't fixed. If you make a new project, could you link to it here, please? I've been thinking of switching to this module from my home made attempt but I need something that works with freetagging.

Thanks,

Michelle

rconstantine’s picture

Sure Michelle, here it is: CCK Taxonomy Super Select Ultra. I don't have time right now, but if anyone would like to get the radio (single select) portion working, that would be great. I'm sure it's easier than I think. Probably a case of staring at it too long on my part.

michelle’s picture

Great, thanks. I love the name, BTW. LOL

Michelle

rconstantine’s picture

I love the name, BTW. LOL

Thanks. All of my other modules have serious names and I thought it was time for an over-the-top name.