Posted by AmrMostafa on September 30, 2009 at 9:18pm
Jump to:
| Project: | More Like This |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I think it would make a lot of sense to have the taxonomy terms prefilled in MLT terms field instead of editors having to pick them one by one for every node. Additionally but not necessarily, there can be a setting per node type allowing the administrator to select which vocabularies to prefill from.
Comments
#1
Anyone have any way of doing this yet? My flikr and google videos have virtually nothing to do with my content...
I'd like to autofill pre-specified terms to my nodes so the correct images/videos come up.
Thanks
#2
I was stumbling on the same problem. I'm using Calais to tag my nodes, set to apply terms on creation, however quite a few suggestions are totally unrelated to the content. I changed my settings to suggest the terms only, however when filling out the MLT terms it doesn't take the existing terms, instead it performs another query to Calais and the result is the same. It would be nice to have the existing terms used or at least on option to chose where to retrieve terms, perhaps have it appear as suggestions which the user can then select.
#3
Same problem here.
Are there any quick solutions to this?
It would be great to prefill MLT search params with node´s current taxonomy-tags.
thanks
#4
I would like to see this, too. Particularly because I'm using community tag to allow users to tag content. It would be great if MLT would use all tags automatically, as soon as they're entered.
#5
Subscribing...
and
@tranquille: I have used the solution in the 10th reply of this post: http://drupal.org/node/384170 and it worked out great. It may not be the cleanest way to go but it is a quick solution to getting the MLT terms prefilled with Calais terms.
#6
I also used the 10th reply of that post. It left me with a bunch of duplicate entries in my DB though.
#7
Are you sure these are duplicates in your DB or just terms being applied twice? The latter causes duplicated listings of the same nodes.
#8
@AlfTheCat + @Mustang302
Thanks for your reply!
I´m still looking for an answer - will try it asap.
#9
yw! :)