Drupal 6 Port
SeanBannister - July 31, 2008 - 10:56
| Project: | Taxonomy Autotagger |
| Version: | 6.x-1.11 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I find this module really useful and was wondering if there's any plans for a Drupal 6 port?
I can help out with testing and possibly a bit of code.

#1
I need this module for a future Drupal 6 project so I'm interested in porting it. But I'm currently porting a few other modules so it might be a while before I get started what could be a good thing as I see the D5 version is still getting a few bug fixes. Please let me know if you're interested in a D6 port or helping out with the port.
#2
chiming in my desire for a D6 version
#3
me 3. i can help with testing.
#4
+1
#5
I could really use a drupal 6 version of this module as well.
#6
edited
#7
Yep, I'm in too. We are about to import a large (content rich) site into D6 and will want to run this module to populate all the new tag fields we'll be using.
#8
+1
#9
+1 for D6 version.
#10
+1
#11
subscribed
#12
Ahem, there's one available, it's far from finished, but is mainly working.
#13
Thanks. I've just tried the 6 version, but wasn't able to get it to work. I haven't loaded the jquery modules yet. Are those necessary for the 6 version? All the checkboxes for autotagging and settings and so on work fine, so I don't think it's a UI issue I'm experiencing. It's just that the nodes aren't getting tagged. Any thoughts? Either way, really look forward to this module.
#14
Just noticed the Drupal 5 version is no longer listed as a release on the Taxonomy Autotagger page, only the new Drupal 6 version is listed.
#15
The D5 version is no longer supported, but can still be downloaded if required.
#16
#17
I understand that it's no longer supported however I was wondering why it was removed from the projects homepage, just because it's unsupported doesn't mean it needs to be removed. A lot of users don't know how to dig past the home page of a project to find other releases. Also I often take a quick look at a modules home page to get an idea of how many Drupal versions the module has been around for, to me the longer a module has been around the greater chance it will stay.
#18
Automatically closed -- issue fixed for two weeks with no activity.