abondoned work on the hierarchy timesink.  Ability to vote on free tagging, and to make hierarchical vocabulary on the fly, still goes where no module has gone before.  Hierarchy and fanciness come in post-production.

actually this commit is cleanup/reorganization and the LAST commit was implementation of CMTs very own version of Drupal 6's db_last_insert_id

tightened up the intro text some more.  Going to the modules page to test uninstall/install I saw what a hog it was.

many changes have been made and not documented while cvs.drupal.org was down.  The previous commit message was quite out of date.  Latest change is tightening up the .info file text.

reversed  and  in cmt_term_attribute_set and cmt_vote and the like: it's far more likely we'll want to override the vote count than the user, and easier to throw a 1 in there for value than to get the current users ID anyway

undid the array_reverse, counting up instead, on traversing through an angle-bracket delimited term set (path)

generalized cmt_term_attribute_set to also take nod nid instead of term tid for setting the cmt_term_node table (which would have been better named node_term, but hey-- this way the function can stay cmt_term_attribute_set and not be a misnomer.  Happy accident.)

Full chain of events following a vote defined up to cmt_term_*_push (renamed functions from cmt_push_term_* for consistency with cmt_term_*_set and the Drupal Way)...  also, cvs commits work a lot better than svn commits when dealing with a cvs repository ;-)

made content_id on each table an auto_increment field (serial CHECK (content_id >= 0)) on PGSQL based on three hours re-reading the great serials/auto-increment debate and ultimately looking at core table declarations and confirming that db_last_insert_id is as simple as it looks

fixed SQL in cmt_get_vocabularies so cmt_enabled matches > 0 -- which in SQL is not the same as = TRUE

fixed silly logic error - missing exclamation point - in form_alter that checked if a vocab was CMT or not, for the create/convert to cmt option.  This error was introduced by the move away from using vocabulary 'ownership' (eg overwriting taxonomy, forum, image etc. indication of whose vocabulary) in favor of inner joining CMT to taxonomy vocab tables.  - ben for agaric  http://drupal.org/project/cmt

that was so strange.  The whole cmt_admin.inc file was refusing to run; best I could determine PHP was not interpreting its spaces as spaces but running everything together.  A Mac-Unix file exchange screw-up?  Anyway, wasted a lot of time, used the content_types.inc from node module as an emptied out file and pasted my content into TextEdit, and then SubEthaEdit (TextWrangler may be the thing screwing it all up) and it works.  Other fixes part of this, most significantly listing multiple new term forms if multiple vocabularies are CMT-enabled.

Division of code into module main functionality and admin pages (cmt_admin.inc), some code cleanup, functionality coming along

a number of fixes so if some fool downloads and installs this pre-alpha module, the administration pages will work (I'd broken everything by changing the basis of a vocabulary being community managed from if the module name assigned to it is cmt, to checking if there's a vid in the cmt_vocabulary table)