| 1 |
$Id: README.txt,v 1.3.2.2 2007/02/02 14:50:04 fago Exp $
|
| 2 |
|
| 3 |
Views Fusion Module
|
| 4 |
------------------------
|
| 5 |
by Wolfgang Ziegler, nuppla@zites.net
|
| 6 |
|
| 7 |
|
| 8 |
Description
|
| 9 |
-----------
|
| 10 |
Views Fusion allows one to fuse multiple views into one. So you can
|
| 11 |
build fusioned views that display information that is stored in multiple
|
| 12 |
nodes - useful for tabular views. It uses node relations for joining the
|
| 13 |
appropriate nodes together.
|
| 14 |
|
| 15 |
So currently the views_fusion module needs the nodefamily module
|
| 16 |
(http://drupal.org/project/nodefamily) for obtaining the node relation
|
| 17 |
information. However in future other node relation modules could also
|
| 18 |
provide their data for views fusion as it is written generic.
|
| 19 |
|
| 20 |
|
| 21 |
Installation
|
| 22 |
------------
|
| 23 |
* Install the latest views module, you need at least version 1.2
|
| 24 |
* Copy the module to your modules directory and activate it.
|
| 25 |
|
| 26 |
Note: You also need a node relation module, e.g. nodefamily.
|
| 27 |
|
| 28 |
|
| 29 |
How to use it
|
| 30 |
-------------
|
| 31 |
First you have to define multiple views, one for each type of nodes. Then
|
| 32 |
the views fusion module is used to fuse these views to a big one which
|
| 33 |
contains all the information.
|
| 34 |
To do this go to 'admin/views/fusion' and define which views you want to
|
| 35 |
fuse and which information you want to use for fusing the views, e.g.
|
| 36 |
use a nodefamily relation.
|
| 37 |
Then have a look at the primary view, it will list the fields of the fused
|
| 38 |
view too.
|
| 39 |
|
| 40 |
Note that you have to select an appropriate node relation which connects
|
| 41 |
the nodes together. If you set a not existing relation, your fused view
|
| 42 |
will have no results. So set this settings carefully.
|
| 43 |
|
| 44 |
|
| 45 |
Notes
|
| 46 |
-----
|
| 47 |
* You have the fuse the views in the correct order. You have to fuse your views
|
| 48 |
in the same order as your chosen relation does work.
|
| 49 |
|
| 50 |
e.g.:
|
| 51 |
ViewA lists nodes of the type 'CD'
|
| 52 |
ViewB lists nodes of the type 'artist'
|
| 53 |
|
| 54 |
Nodefamily creates a relation between some of them, where CDs are parents and
|
| 55 |
artists their children.
|
| 56 |
|
| 57 |
Then you can create a fusion by using ViewA as primary view, fused with ViewB
|
| 58 |
using the nodefamily parent - child relation.
|
| 59 |
Or you can also create a fusion in the reverse direction: Use ViewB as primary
|
| 60 |
view, fused with ViewA using the nodefamily child - parent relation.
|
| 61 |
|
| 62 |
|
| 63 |
* Currently it's not possible to alter the order of single fields of a tabular
|
| 64 |
view over the whole view. The first field of a fused view will always be displayed
|
| 65 |
behind the last field of the primary view.
|
| 66 |
This also applies to any sort critera you might have set for the views. So the sort
|
| 67 |
criteria of the primary view will have precedence over the sort criteria from the
|
| 68 |
fused view.
|
| 69 |
However the order of the fields can still be customized by theming the view.
|
| 70 |
|
| 71 |
|
| 72 |
Restrictions & Problems
|
| 73 |
-----------------------
|
| 74 |
* Argument Handlers for fused views are not supported! You may only use argument handlers
|
| 75 |
on the primary view.
|
| 76 |
* Some fields don't work properly with views_fusion. Currently known to not work are:
|
| 77 |
|
| 78 |
* CCK fields for multiple fields, which are set to "group multiple values"
|
| 79 |
|
| 80 |
* If you discover further not working fields or filters, please open an issue for them in
|
| 81 |
the views fusion issue queue, so I can fix them or add them here.
|
| 82 |
|
Parent Directory
| 
Revision Log
| 
Revision Graph