Downloads
Release notes
Note: Be sure to run update.php!
This release probably best explained by an email I sent to co-maintainer @entrigan earlier:
"For this release the main area of focus was on making sure that community tags has a solid foundation on which to add new features and port to D7. I had a pretty thorough look at the various workflows that should involve community tags and found that a bit of work was needed - I made some notes in the README.txt so that the expected behaviour was documented - I should write some tests really.
Basically I didn't like the use of wholesale delete/re-insert when adding/removing 1 tag. As an example the Amazon Kindle (on Amazon) has about 3000 tags - CT would handle a single tag event on this by deleting and re-inserting all 3000 of them - and all during a AJAX call.
The other thing I didn't like was the rehash function and the way it would delete as many community tags as it could every time the CT settings page was hit. If you disabled CT on a vocab for whatever reason - all ctags for that vocabulary would be deleted without warning. So I replaced that with a configuration page that allows you to delete tags if you don't need them anymore and rebuild tags if for any reason they need rebuilding (config changes or direct database fiddling etc). The rebuild and delete are batched so that dependent actions - e.g. term, term node (potentially rule based) can fire without causing a time out on large tag sets.
Most shortcomings have been raised as bugs/feature requests and most of which I have addressed. The feature requests I have added have been under the hood - e.g. adding configuration options that affect what happens when a tag is added/deleted. The behaviour of the default configuration is unchanged and anybody upgrading shouldn't notice any difference.
I have removed the dependence on Tagadelic but, again in an effort to make it work as per 1.x, if Tagadelic is installed then it will use it by default unless the administrator chooses to display tags as simple links (as per patch submitted by coltrane) or not display them at all which has been requested by somebody else. I implemented this in a very basic non-extensible way, but having read some of your comments on the matter, that is definitely an area for 2.x dev.
Other improvements are: multiple CT vocabs per node type, always calling node_save when CT adds term to node which allows several other modules to work with CT, responding to node, user, and term delete operations, not attributing all tags to node author on node save etc...
It may sound like a lot of changes, but it's all under the hood with no apparent differences to the user (apart from fixes to errarnt behaviour). Even the admin doesn't need to do anything on upgrading. Which is why (and I'm selling it hard here) I'd like to commit these changes to the DRUPAL-6--1 branch and make a beta-4 release pending an official stable 1.x release. That will leave the 2.x branch for lots of new features without the pressure to get a stable release out, and HEAD for D7 development. Otherwise we could leave 1.x hanging as unstable, make the stable release on 2.x and start a 3.x for further feature development."
And a list of issues covered by this release (there may be others):
#984496: Saving from the node edit form ascribes all existing tags (regardless of whether new ones are added) to the user who is editing
#655354: Community tags and apache solr search
#975752: Conflict between tags added from node EDIT area
#984462: When a tag is no longer attached to any nodes, (provide option to) automatically remove it from its taxonomy vocabulary - check the "sync terms" option on the configuration page.
#199936: Support more than one vocabulary per node type
#644640: quick form submit doesn't node save
#1056314: Remove the "All Tags" list. - set display to none on configuration page.
#799136: Some performance tweaking
#149254: Tagadelic required? - select display type on configuration page.
#359024: community_tags_rehash optimization patch (Fixing rehash timeout when changing admin settings) - rehash no longer called.
#361510: It doesn't respect the content types vocabulary settings
