Hi,

Again thanks for the great module. After converting my already available terms to work with cck_field I can work great with this module. On IE 6 it says that the process time of the query is too much, but on firefox the module works great.

The only thing is that the terms which are created on /add/node with freetagging and parent chosing do not have the url-alias as normal terms do. Is this an easy to correct error? Could you otherwise tell me how I can change the module so it will use the url-alias (the inserted term-name with the installation as stated in the pathauto module)?

Thanks again for this great module, finally able to add nodes and terms on the same page!

Greetings,
Martijn

Comments

rconstantine’s picture

rconstantine commented

I was going to get around to your other issue today, but by your comment here, it sounds like you got the data copied just fine. Is that correct? If so, could you make a comment to your other post about that?

I know of the issue on IE6. How large is the vocab you are using? If I can ever get around to adding AJAX support, then this problem will go away since I'll only load 'open' branches.

I am not sure what you mean by url-alias of terms. Is that a normal function of the taxonomy module, or does another module provide that? How does it work normally? Do you have the option set from this module to treat terms as regular tags? I see that you mention the pathauto module. Is that what creates the url-aliases? Are you wanting the aliases to be displayed? Please explain. Screen shots would help.

summit’s picture

summit commented

Hi Ryan,

Yes I got the terms converted..but what if I use for one contenttype your great module, and for another contenttype the regular taxonomy vocabulary because it loads faster. the terms are then not synchronised. So I think it is a short term solution, so please get into a modulewise solution so when the module is running it gets the terms from the node which is loaded/updated.

I am using a regional vocabulary of a lot of places of the world, so say about 1000 terms...+1 for ajax support!

Yes it is pathauto which does the url-aliassing. When I add a term on the normal basis, through admin/content/taxonomy I can fill in a term name and than pathauto makes the taxonomy/term/[tid] aliassed to the term name.
I think this needs to be done also on cck_taxonomy_ssu.

I got through cck_taxonomy_ssu the term as term/taxonomy/230 displayed when I click on the new added term, instead of /category/trekking Category is my vocabulary and trekking is my term-name. The pathauto module builds /category/trekking of it because of the rule: [vocab-raw]/[catpath-raw]
Yes I want the aliases to display exactly as term-adding through admin/content/taxonomy does using the pathauto module.

Thanks a lot for going into this!

greetings,
Martijn

rconstantine’s picture

rconstantine commented
Title: Freetaggging with parent url-alias not working (pathauto support?) » (pathauto support) Freetaggging with parent url-alias not working
Category: support » feature

Changing to a feature request. Sounds like a good feature to add. Hopefully, there is just a hook or two that needs to be employed.

On another subject, I want to make sure you understand that now that you have copied data from the old nodes to the new, that for new nodes, if you are using this module's feature that allows 'regular tags' (or whatever I called it), that the same table that the taxonomy module uses will be updated and tags will show on your nodes (old and new) as they always have. Using this module in conjunction with another module that does a similar thing, on the other hand, will not work in any clean way, nor will that ever be supported.

So, in the future, we'll have an import feature for adding this module to an existing site, but not support for co-existing with similar modules. Also, we'll have AJAX for loading large vocabs in smaller chunks. And like I said, you should have the option now of having your tags behave like regular taxonomy tags.

summit’s picture

summit commented
Component: Code » Miscellaneous

Hi Ryan,
I understand what you are saying.
So it is not possible to use this module for a contenttype AND the normal taxonomy.module vocabulary for say another contenttype. Is that what you are saying? Than clear for me. Thanks for explaining.

If so, than the AJAX working would very much be appreciated to get the fastest way to show the terms and to select from them.
Again thanks for your quick reply!
Greetings,
Martijn

rconstantine’s picture

rconstantine commented

That's not what I'm saying. The normal taxonomy module and this one play nice together, but don't share information. In fact, this module uses some taxonomy functions and so, if I didn't already adjust the info file to reflect that the taxonomy module is required, I should. Other modules, like taxonomy_cck may or may not play nice together and are not designed to.

rconstantine’s picture

rconstantine commented

OK. So I'm starting to look at this. I think in my module, I'm INSERTING directly into some of the taxonomy tables. I'm guessing that if I replace that code with calls to taxonomy functions, that pathauto will then work without me doing anything special.

In any case, I'm working on this right now.

rconstantine’s picture

rconstantine commented
Status: Active » Fixed

Done, but another bug was introduced since I no longer know what the new TID is. I'll track that down too. Look for a release soon.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.