Download & Extend
Node Auto Term [NAT] » Issues

Token module integration

Posted by ray007 on May 29, 2007 at 3:47pm
Project:Node Auto Term [NAT]
Version:6.x-1.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:needs work

Issue Summary

The attached little patch provides token support to generate the string for the term.
This happens on node-insert and -update.

It does not (yet) generate the terms from the pattern on sync.
It still generates a single term, and not a path hierarchy.

Comments?

AttachmentSize
nat-token-support-1.patch3.23 KB
Login or register to post comments

Comments

#1

Posted by Zen on May 30, 2007 at 8:36pm
Status:needs review» needs work

At the risk of repeating myself, please provide a use case :) It looks very flexible, but what are you going to use it for?

I can't test the patch as the path is incorrect : "a/nat".

Thanks Ray.
-K

#2

Posted by Zen on May 30, 2007 at 8:41pm

I just saw your other issue. Marking that one a dupe of this.

- have checkboxes instead of select-list to be able to activate/deactivate a custom term-generation per contenttype/vocabulary
- instead of just creating a term by title have a text field for entering a category-path interpreted by the token-module

I don't understand what you mean about checkboxes being better. How?

Category path: This sounds like a good idea. I will test this patch once you re-roll it. I'd also appreciate it if you can provide an example use case and perhaps steps to test it out.

Cheers.
-K

#3

Posted by ray007 on May 30, 2007 at 10:08pm

The checkboxes instead of select-list are necessary if we'd like to have a pattern per node-term association. But in that case the userinterface probably needs an overhaul.

What am I going to use it for: the plan is to use node_autotitle to generate the title from several fields (you could say: combination of an ID and a subtitle), and I'd like to use the id-field to generate the term-entry.

I don't yet need the category-path right now and the patch to do that would be a bit more involved, so am postponing that for now.

I've also skipped the sync operation for now since I have no idea what you do with the node_revisions there.

And for testing the patch: please use 'patch -p1 ...' ;-)

#4

Posted by ray007 on June 21, 2007 at 12:42pm

Still no path-support, but should work for sync operations now too.
New patch against current head.

Ok this way?

AttachmentSize
nat-token-support-2.patch 3.9 KB

#5

Posted by ray007 on July 20, 2007 at 6:21am

*Bump*

Anything wrong with the patch?

#6

Posted by Summit on November 24, 2008 at 11:34am

Subscribing,
is this committed please?
Thanks a lot in advance for considering this!

greetings,
Martijn

#7

Posted by anantagati on March 4, 2010 at 10:08pm
Title:token support part 1» Token module integration
Version:master» 6.x-1.x-dev
Category:task» feature request

Looks like interesting feature.

#8

Posted by gagarine on May 16, 2010 at 1:15am

tracking

#9

Posted by stefan81 on October 18, 2010 at 5:57am

Hello!

Probably I am in the right thread,
If not, I'll create a new one ;)

I would like to use a Token in Pathauto respectively "Automated alias settings" for my NAT node types.
Something like [NAT-vocab-raw] and [NAT-catpath-raw]

The token should grab the [vocab-raw] and the [catpath-raw] of the taxonomy term, which NAT node is referring to.

Is that possible?

nobody click here