Posted by taite11 on May 2, 2009 at 7:34pm
Jump to:
| Project: | Taxonomy Filter |
| Version: | 7.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | solotandem |
| Status: | closed (fixed) |
Issue Summary
I would like to be able to not show terms unless they match at least 2 nodes. It would be better still if I could select the minimum threshhold to show the tags at.
I am using the tag cloud to display tags added by users. Sometimes they add useless or spammy tags so I would like to only show terms if they have at least 2 matches. For example, a user will add tags that are too long or they will add too many tags or they will add misspelled tags.
Comments
#1
This seems like a useful feature. I will add this in an upcoming release. Thanks.
#2
Subscribe
#3
Implemented in next dev release.
You need to run database update and then set values at admin/settings/taxonomy_filter/%/edit.
Test it and let me know if this works for you.
#4
I tried it. On database update it didn't show any updates. That is, the progress bar showed "0 of 0 updates".
There are no added settings on admin/settings/taxonomy_filter/%/edit.
I'm using the "cloud" menu template.
#5
Based on the timestamp of your comment, it would appear the dev release had not been updated. The last release update is:
Last updated: January 6, 2010 - 07:18
Download the dev release and try again.
#6
It works, but there is a bug too.
This time it said this on update:
"The following queries were executed
taxonomy_filter module
Update #6004
* No queries"
The new fields are on the admin/settings/taxonomy_filter/%/edit page.
I tested it using a "minimum node count" of 2 and 3 and it worked.
I noticed then when I went back to admin/settings/taxonomy_filter/%/edit, it reset the "minimum node count" to 0.
I then changed the "minimum node count" to 2, went back to admin/settings/taxonomy_filter/%/edit, checked the page with the block and it didn't work anymore.
I realized that if I go back to admin/settings/taxonomy_filter/%/edit, even if I don't make any changes or click "save settings", the settings are lost.
Block cache and other caching are turned off for this site. I'm using the cloud menu.
#7
The no queries message is fine. Drupal's update page (this is changed in D7) always wants a query to run even though the update code may not execute one directly (which is the case here). All this is doing is updating an entry in the variables table using Drupal API functions. I do not experience the setting reverting to zero. Are you sure about this?
#8
I'm sure that the settings are reset to 0 when I check that page on my site. Drupal 6.10. I tried that many times to make sure.
#9
Changed in next dev release created after this comment to allow user input of the value.
I can not reproduce your issue with the input values being set back to zero.
Test it and let me know if this works for you.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.
#11
This works for me now after upgrading core to 6.16. It's a really great feature.