You are here

README.txt in Insert View 6

Same filename and directory in other branches
  1. 8 README.txt
  2. 5 README.txt
  3. 6.2 README.txt
  4. 7.2 README.txt
  5. 2.0.x README.txt
OVERVIEW
--------
The Views module allows administrators to create dynamic lists of content
for display in pages or blocks. It is possible to insert those lists into
existing node bodies and blocks, but such inclusion requires that PHP
filtering be turned on. The Insert View module allows any user to insert
view listings using tag syntax, without the need for PHP execution
permissions. The Insert View tag syntax for embedding a view is relatively
simple.

[view:my_view]
is replaced by the content listing corresponding to the named view. In this
case it is my_view.

[view:my_view=my_display]
invokes the my_view view using the my_display view display ID. If the display
slot is left empty, the view\'s "default" display is used.

See "HOW TO FIND A DISPLAY ID" below for help with display IDs.

Note: the display slot was previously used (in the Drupal 5 version) to provide
numeric limiters to control the number of nodes to display in a view. This sort
of local override has been deprecated in favor of taking advantage of Views
version 2's custom display functionality. See "UPGRADING FROM A PREVIOUS
VERSION" below for more information.

[view:my_view=my_display=1,2,3]
uses the my_display view display, and passes a comma delimited list of arguments
(in this case 1, 2, and 3) to the view.

Here's an example you could use with the default view named "tracker" which
uses the page display and takes a user ID as an argument:

[view:tracker=page=1]

In short this tag says, "Insert the view named tracker, use the "page" display,
and supply the argument 1."

Sometimes you want to pass an argument without specifying a display ID. You can
do that by leaving the display ID slot empty, like so:

[view:my_view==1]

In previous versions you could use the [view_pager:my_view] tag. It has been
deprecated in the Drupal 6 branch in favor of using views displays. See
"UPGRADING FROM A PREVIOUS VERSION" below for more information.

HOW TO FIND A DISPLAY ID
------------------------
On the edit page for the view in question, you'll find a list of displays at the
left side of the control area. "Defaults" will be at the top of that list. Hover
your mouse pointer over the name of the display you want to use. A URL will
appear in the status bar of your browser.  This is usually at the bottom of the
window, in the chrome. Everything after #views-tab- is the display ID. For
example in http://localhost/admin/build/views/edit/tracker?destination=node%2F51#views-tab-page
the display ID would be "page".

INSTALLATION
------------
Extract and save the Insert View folder in your site's modules folder and enable
it at admin/build/modules. Obviously, it requires the Views module to do its
magic.

Once Insert View is installed, visit the the input formats page at
/admin/settings/filters and click the "configure" link for the input format(s)
for which you wish to enable the Insert View Filter.  Then simply check the
checkbox for the filter.

IMPORTANT PERFORMANCE NOTE: To dispaly views correctly, Insert View turns off
caching for the input formats for which it is enabled. That means every node
using this input format will not be cacheable. This can impact site performance.
In these cases, it is recommended to create a special input format for use when
inserting views.

UPGRADING FROM A PREVIOUS VERSION?
----------------------------------
IF YOU UPGRADED FROM THE DRUPAL 5 VERSION OF INSERT VIEW:

THE LIMITERS SLOT IS NOW USED FOR DISPLAYS
Previously in Insert View the display slot was used to provide a numeric value
representing the number of nodes to display when showing the view. This has been
deprecated due to changes in Views version 2. With the ability to create custom
displays, we can use Views' functionality to make a unique view display to use
with Insert View. ALL EXISTING VIEWS USING THE NUMBER LIMITERS SHOULD CONTINUE
TO WORK, BUT WILL BE BASED OFF THEIR VIEWS' DEFAULT DISPLAY.

VIEW_PAGER SYNTAX HAS BEEN DEPRECATED
Previously in the Drupal 5 version, Insert View tags such as the one below could
be used to control the use of pagers in views. As of the Drupal 6 version,
however, you should simply use the settings in your views display to set the
pager. If your inserted view will require pager settings different than the base
view settings, simply create a new display via the Views interface and override
those settings.

Example of the deprecated tag: [view_pager:<name of view>=<number>]

CHANGES WITHIN THE DRUPAL 5 BRANCH OF INSERT VIEW:

In previous versions of Insert View (including the 2008-Jan-11 development snapshot
and earlier) it was was not required to enable the Insert View filter for input formats
(by visiting the /admin/settings/filters pages) because Insert View was a pseudo filter
and used hook_nodeapi() rather than the filter system.

Insert View now runs as a classic Drupal filter module, and that means it now works
in blocks.  If you upgrade your site and find Insert View tags aren't working, please
visit /admin/settings/filters and enable the Insert View Filter for each input format
necessary.

File

README.txt
View source
  1. OVERVIEW
  2. --------
  3. The Views module allows administrators to create dynamic lists of content
  4. for display in pages or blocks. It is possible to insert those lists into
  5. existing node bodies and blocks, but such inclusion requires that PHP
  6. filtering be turned on. The Insert View module allows any user to insert
  7. view listings using tag syntax, without the need for PHP execution
  8. permissions. The Insert View tag syntax for embedding a view is relatively
  9. simple.
  10. [view:my_view]
  11. is replaced by the content listing corresponding to the named view. In this
  12. case it is my_view.
  13. [view:my_view=my_display]
  14. invokes the my_view view using the my_display view display ID. If the display
  15. slot is left empty, the view\'s "default" display is used.
  16. See "HOW TO FIND A DISPLAY ID" below for help with display IDs.
  17. Note: the display slot was previously used (in the Drupal 5 version) to provide
  18. numeric limiters to control the number of nodes to display in a view. This sort
  19. of local override has been deprecated in favor of taking advantage of Views
  20. version 2's custom display functionality. See "UPGRADING FROM A PREVIOUS
  21. VERSION" below for more information.
  22. [view:my_view=my_display=1,2,3]
  23. uses the my_display view display, and passes a comma delimited list of arguments
  24. (in this case 1, 2, and 3) to the view.
  25. Here's an example you could use with the default view named "tracker" which
  26. uses the page display and takes a user ID as an argument:
  27. [view:tracker=page=1]
  28. In short this tag says, "Insert the view named tracker, use the "page" display,
  29. and supply the argument 1."
  30. Sometimes you want to pass an argument without specifying a display ID. You can
  31. do that by leaving the display ID slot empty, like so:
  32. [view:my_view==1]
  33. In previous versions you could use the [view_pager:my_view] tag. It has been
  34. deprecated in the Drupal 6 branch in favor of using views displays. See
  35. "UPGRADING FROM A PREVIOUS VERSION" below for more information.
  36. HOW TO FIND A DISPLAY ID
  37. ------------------------
  38. On the edit page for the view in question, you'll find a list of displays at the
  39. left side of the control area. "Defaults" will be at the top of that list. Hover
  40. your mouse pointer over the name of the display you want to use. A URL will
  41. appear in the status bar of your browser. This is usually at the bottom of the
  42. window, in the chrome. Everything after #views-tab- is the display ID. For
  43. example in http://localhost/admin/build/views/edit/tracker?destination=node%2F51#views-tab-page
  44. the display ID would be "page".
  45. INSTALLATION
  46. ------------
  47. Extract and save the Insert View folder in your site's modules folder and enable
  48. it at admin/build/modules. Obviously, it requires the Views module to do its
  49. magic.
  50. Once Insert View is installed, visit the the input formats page at
  51. /admin/settings/filters and click the "configure" link for the input format(s)
  52. for which you wish to enable the Insert View Filter. Then simply check the
  53. checkbox for the filter.
  54. IMPORTANT PERFORMANCE NOTE: To dispaly views correctly, Insert View turns off
  55. caching for the input formats for which it is enabled. That means every node
  56. using this input format will not be cacheable. This can impact site performance.
  57. In these cases, it is recommended to create a special input format for use when
  58. inserting views.
  59. UPGRADING FROM A PREVIOUS VERSION?
  60. ----------------------------------
  61. IF YOU UPGRADED FROM THE DRUPAL 5 VERSION OF INSERT VIEW:
  62. THE LIMITERS SLOT IS NOW USED FOR DISPLAYS
  63. Previously in Insert View the display slot was used to provide a numeric value
  64. representing the number of nodes to display when showing the view. This has been
  65. deprecated due to changes in Views version 2. With the ability to create custom
  66. displays, we can use Views' functionality to make a unique view display to use
  67. with Insert View. ALL EXISTING VIEWS USING THE NUMBER LIMITERS SHOULD CONTINUE
  68. TO WORK, BUT WILL BE BASED OFF THEIR VIEWS' DEFAULT DISPLAY.
  69. VIEW_PAGER SYNTAX HAS BEEN DEPRECATED
  70. Previously in the Drupal 5 version, Insert View tags such as the one below could
  71. be used to control the use of pagers in views. As of the Drupal 6 version,
  72. however, you should simply use the settings in your views display to set the
  73. pager. If your inserted view will require pager settings different than the base
  74. view settings, simply create a new display via the Views interface and override
  75. those settings.
  76. Example of the deprecated tag: [view_pager:=]
  77. CHANGES WITHIN THE DRUPAL 5 BRANCH OF INSERT VIEW:
  78. In previous versions of Insert View (including the 2008-Jan-11 development snapshot
  79. and earlier) it was was not required to enable the Insert View filter for input formats
  80. (by visiting the /admin/settings/filters pages) because Insert View was a pseudo filter
  81. and used hook_nodeapi() rather than the filter system.
  82. Insert View now runs as a classic Drupal filter module, and that means it now works
  83. in blocks. If you upgrade your site and find Insert View tags aren't working, please
  84. visit /admin/settings/filters and enable the Insert View Filter for each input format
  85. necessary.