Closed (fixed)
Project:
Similar By Terms
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Sep 2007 at 14:11 UTC
Updated:
4 Jul 2008 at 00:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
jjeff commentedI like this idea.
Keep in mind that you can get some of this functionality simply by assigning your vocabularies only to certain node types. For instance, if you have a vocabulary called "blog tags" that's only assigned to blog content, then page or story content items won't show up (as they won't have any matching tags in that vocabulary)...
However, I could see a use for this in certain cases. So I'll keep an eye out for your patch.
Comment #2
alfaguru commentedOK, patch attached. I'm passing in a single nodetype with a default of null. I could have used different vocabularies for different content types but that did not seem a natural solution. And the change is really very simple, although there might be a neater way to code it.
Comment #3
nath commentedThis is something we need. We have multiple content types all using the same vocabulary but only node types from one content type should be displayed in one of the blocks.
Thanks for the patch, that does one part of the needed changes. I guess, in addition to this I need to change the block configuration so that one can choose the content type to be displayed.
Comment #4
nath commentedI have added the following code to the form configuration so that I'm able to chose a content type to display in the block.
Comment #5
Christefano-oldaccount commentedThe patch at #2 no longer applies and wasn't marked "needs review" (and the code in #4 wasn't in it anyway), and I hate to think this issue is disappearing into a black hole. I think the idea is a good one, though, and hope others will have a chance to see what all the excitement is about.
Comment #6
Christefano-oldaccount commentedI like this patch a lot. It works perfectly and doesn't disrupt any existing functionality. I'd like to have the option of selecting more than one content type, though. Currently the selection only allows one content type.
Comment #7
miiimoooThis version of similarterms adds supprot for choosing multiple content types AND the same content type as the currently displayed node is of.
Go into the block settings and select the content types you want the block to display.
Hope you find this useful.
Comment #8
Christefano-oldaccount commentedI'll test this soon (it would help if it were a patch, though). Thanks, miimooo!
Comment #9
Christefano-oldaccount commentedHere it is as a patch. I'll start testing it tomorrow or the next day.
Comment #10
Kripsy commentedThe patch works great so far. My only concern right now is duplicating the "Similar entries from ANY vocabulary" block so that I can have different blocks for finding related material from different node types. Any ideas?
Comment #11
goosemoose commented$form['type'] = array(
'#type' => 'radios',
'#title' => t('Display nodes of this type'),
'#options' => node_get_types('names'),
'#default_value' => variable_get('simterms_type_'. $delta, ''),
'#description' => t('Only nodes of this type will be displayed in this block.'),
);
This is exactly what I need to filter blocks but where did you add it?
Comment #12
jrabeemer commentedAwesomeness. Where is jjeff?
Comment #13
summit commentedSubscribing, +1 to get this in! greetings, Martijn
Comment #14
rmiddle commentedThis sounds like a neat Idea.
Comment #15
Rob T commentedI'd love to see this in the 6.x version.
Comment #16
rmiddle commentedI need to do some testing before I can put this in. Leave open for review.
Comment #17
rmiddle commentedOk I lied it is in CVS and will be included in the 1.3 release.
Thanks
Robert
Comment #18
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.