Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Would it be possible implement multiple RelatedContent view(s) on
admin/content/types/page
where; instead of radio button
------------------------------------------------------
RelatedContent settings
Configure how RelatedContent should work on nodes of the type page. For more information, see the help page.
RelatedContent view (s): all current views are presented with a tickbox instead of a radio button
[X] viewA
[X] viewB
[X] viewC ... so on
Select a view that will provide the node list. Leave empty to disable RelatedContent.
Comment | File | Size | Author |
---|---|---|---|
#4 | RelatedContent-1.png | 34.83 KB | TBarregren |
#4 | RelatedContent-2.png | 54.32 KB | TBarregren |
Comments
Comment #1
ica CreditAttribution: ica commentedopps.. sorry i mean multiple RelatedContent view(s) with tick boxes instead of drop down options (as currently is) NOT radio buttons
Comment #2
TBarregren CreditAttribution: TBarregren commentedI am start working on it along with some other improvements.
Comment #3
jgumpert CreditAttribution: jgumpert commentedI'm very interested in this enhancement too - glad to see it is being addressed!
Would the end result be that the node creator first picks the view to use from a list of available views for that content type and then the 'node edit' page updates (maybe with JQuery or some other means) to show the list of nodes available in the selected view?
Comment #4
TBarregren CreditAttribution: TBarregren commentedA picture is worth a thousand words... I have attached two screenshots from the next version of RelatedContent. I expect to release it next week (w 4).
Comment #5
TBarregren CreditAttribution: TBarregren commentedThis is implemented in the upcoming 1.6 version. You can download it from here: http://drupal.org/node/214576.
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.