"Free tagging"/folksonomy backported to 4.6

That's one off my wish list. Thank you so much for this. I wanted this feature so badly I was tempted to use the folksonomy module, but I figured that might give me trouble upgrading to 4.7. And I thought it might come out in core in 4.6.1, something like a month or two away.

Anyway, I'm going to try this this evening and report back if it goes ok.

Two things:

1. Free-tag vocabularies are wonderful for use as the image navigation vocabulary, but you really need to apply this patch and create the image vocabulary before installing image.module, if you can. Otherwise, you need to go into the database manually and toggle the auto-created one from image.module to be a free-tagged one. (It looks as if the latest version of Morbus' patch allows you to do this from the web UI, but I haven't tested this exhaustively. So maybe this is no longer an issue.)
2. My upcoming mass-import module for images, image_import.module, specifically exploits Morbus' patch if available. I've been working with it a lot and highly recommend it. +1 indeed!

Scott

Anybody interested in free tagging in the aggregator module?

The use case in my mind is for shared blogs/aggregators based on drupal where people read news. Tagging them in another way than the predefined categories can help getting what's hot without posting.
Kind of a local technorati but with a limited lifespan (aggregated news are deleted after sometime if I am not wrong).

Other approach would be to enable tagging from the aggregated view, it would automatically post a blog node with the news link in it and propose to add text.
As it is for a multiuser application, the aggregator should be aware of the fact that a news has been already blogged. So if others want to tag the news from the aggregator, they actually modify/add tags to this node and can add a comment.

Just a thought based on how we use RSS feeds and drupal within my company.

I'm having an incredibly hard time patching the file on the server. Would anyone be willing simply to email me the updated taxonomy.module? Or is it posted anywhere?

Thanks,

John

Hi, just wondering if there was a quick and dirty (or slow and clean...) way of making individual tag entry during node creation spaces instead of commas... most sites which use tagging use spaces, and not commas.

Thanks!

s.

Something else that would be great would be tag URL aliases... basically, instead of each tag still being "taxonomy/term/45", it would be "tag/puppies".

This would allow anyone to quickly see all terms with a certain tag simply by going to http://site.com/tags/puppies, "just like on" (must love it when people say that...) TagSurf, del.icio.us and Flickr.

Maybe this could actually be done by using some stuff from the pathauto.module?

I tried updating my taxonomy module to use free tagging but it didn't work. It fails on the database/update.inc patch part. Is there a way to attach a file to this posting so I can post my update.inc file?

Before I dig into how I could actually apply this patch, I was wondering if using this patch will complicated the 4.7 upgrade.

Anybody have a patched version of 4.6.3 taxonomy for this they can post or email.

I've had to modify he maxlength of the input box to a much larger value since I use ALOT of tags on my nodes.

See http://merlib.org/node/1092/ for instance

I just updated and reapplied the patch to 4.6.4 and there do not seem to be any problems.

Hi,

I added this patch to show a text area with already defined tags, so the user can look at and choose one before introducing new ones.

Replace this code:

      $typed_string = implode(', ', $typed_terms) . (array_key_exists('tags', $terms) ? $terms['tags'][$vocabulary->vid] : NULL);
      $result[] = form_textfield($vocabulary->name, 'taxonomy][tags]['. $vocabulary->vid, $typed_string, 50, 100, t('A comma-separated list of terms describing this content (Example: funny, bungie jumping, "Company, Inc.").'), NULL, ($vocabulary->required ? TRUE : FALSE));

with this one

      $typed_string = implode(', ', $typed_terms) . (array_key_exists('tags', $terms) ? $terms['tags'][$vocabulary->vid] : NULL);
      $result[] = form_textfield($vocabulary->name, 'taxonomy][tags]['. $vocabulary->vid, $typed_string, 50, 100, t('A comma-separated list of terms describing this content (Example: funny, bungie jumping, "Company, Inc.").'), NULL, ($vocabulary->required ? TRUE : FALSE));
      
      // saoma added
      $allTerms = array();
      $children = taxonomy_get_tree($vocabulary->vid);
      foreach ($children as $term) {
        $allTerms[] = $term->name;
      }      
      $result[] = form_textarea(t("Existing ").$vocabulary->name, 
                                  "saoma_all_terms", // add this name to tinymce.module to disable rich-editing on this textarea
                                  implode(', ', $allTerms), 
                                  50, 4, 
                                  t("Existing tags in %voc_name. Before introducing new tags, please look at this list of already defined tags if you can reuse some of them.", array('%voc_name' => $vocabulary->name)),
                                  NULL);

in your patched taxonomy.module.

Cheers :).

When applying the patch to the Drupal 4.6.5 taxonomy.module, foreign taxonomy vocabularies mysteriously disappear from the categories list. With 'foreign' I mean vocabularies that were created by modules other than the taxonomy module itself, such as the forum module and the userstag module (from GoJoinGo). When putting back the original 4.6.5 taxonomy module, the vocabularies re-appear.

Is this a known side effect of the patch and if so, is there a remedy available?

note this patch does not work on a civicspace distribution because the databas has a different name. google on civicspace free tagging and you will find that patch. it has a mysql file that you will need to process. I got an error that hunk #13 failed but I checked the line number and it seemed to deal with help text so I thought it may not be crucial.

Right now free tagging seems to be working. know that you have to enable it through administer--categories--add vocabulary (see Robert Douglas book on Drupal)

I am about to dive into this and feeling entirely wiggly about the prospect. Here is what I think understand:

* this patch is still not part of the 4.6.x core, so I do need the patch if I want to use freetagging on any 4.6.x site and specifically on my 4.6.6 site.

* The patch I want is "freetag-4_6_3.patch" from Morbus's sandbox.

* I don't want taxonomy_all.patch or taxonomy_all_5.patch (both from http://drupal.org/node/19697) -- those are old?

The patch appears to patch, among other things, /database/database.mysql -- my table definitions. Is there somewhere, an "alter table" script that I can use if I am trying to get this running on an existing 4.6.6 site? Or is that where update.php comes in?

These feel like dumb questions but I keep reading this page and the discussion of the taxonomy_all.patch files and I find that I am still entirely confused.

Thanks,
Amanda

I didn't see any obvious link to a seperate patch, just a circular clickpath that leads back to this thread. Can you post a link to the CS-specific patch?

Would it be possible to use this code from 4.7 to have auto-completion for the field?:

function taxonomy_autocomplete($vid, $string = '') {
  // The user enters a comma-separated list of tags. We only autocomplete the last tag.
  // This regexp allows the following types of user input:
  // this, "somecmpany, llc", "and ""this"" w,o.rks", foo bar
  $regexp = '%(?:^|,\ *)("(?>[^"]*)(?>""[^"]* )*"|(?: [^",]*))%x';
  preg_match_all($regexp, $string, $matches);
  $array = $matches[1];

  // Fetch last tag
  $last_string = trim(array_pop($array));
  if ($last_string != '') {
    $result = db_query_range("SELECT name FROM {term_data} WHERE vid = %d AND LOWER(name) LIKE LOWER('%%%s%%')", $vid, $last_string, 0, 10);

    $prefix = count($array) ? implode(', ', $array) .', ' : '';

    $matches = array();
    while ($tag = db_fetch_object($result)) {
      $n = $tag->name;
      // Commas and quotes in terms are special cases, so encode 'em.
      if (preg_match('/,/', $tag->name) || preg_match('/"/', $tag->name)) {
        $n = '"'. preg_replace('/"/', '""', $tag->name) .'"';
      }
      $matches[$prefix . $n] = check_plain($tag->name);
    }
    print drupal_to_js($matches);
    exit();
  }
}