Closed (won't fix)
Project:
Insert View
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 May 2008 at 12:43 UTC
Updated:
30 Mar 2009 at 21:22 UTC
Jump to comment: Most recent
Comments
Comment #1
mlsamuelson commentedAnselm Heaton,
Unfortunately, deciding the type of view is a little too far upstream for Insert View to affect in its current state... not saying it can't be done, but this isn't a planned feature.
I'll leave the issue active for a while in case an outpouring of support for the feature should occur. Or someone decides to supply a patch. Otherwise, I'll probably mark it as "won't fix" in a month or so.
Glad you like the module, Anselm!
mlsamuelson
Comment #2
pasqualleThere are too many things in the views module, the insert_view can't support every property in it.
Setting the view style is not enough to determine how the view should be displayed. For example if you change the style from list to table view then you have new options like which field is sortable and so on..
Sorry, this request can't be solved with insert_view..
Comment #3
Anonymous (not verified) commentedAs has been said this is probably beyond insert view.
But a simple solution to originators problem, I assume they would want some control over their users ability to affect the content format on their site, so why not create the view display variants "list, as a table, as node teasers etc" wich would be a very simple variation of the default display.
Then the user can insert using
[view:name of view=name of display]
sustituting the name of display as required