token support part 1

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

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

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 ...' ;-)

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

Ok this way?

*Bump*

Anything wrong with the patch?

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

greetings,
Martijn