| 1 |
Requirements
|
| 2 |
------------
|
| 3 |
|
| 4 |
This module requires Drupal 5 or higher.
|
| 5 |
|
| 6 |
Installation
|
| 7 |
------------
|
| 8 |
|
| 9 |
1. Place the event module with all its files under modules/event.
|
| 10 |
|
| 11 |
2. Enable the module in admin >> site configuration >> modules
|
| 12 |
and set the module settings to your liking in
|
| 13 |
admin >> site configuration >> modules >> event.
|
| 14 |
|
| 15 |
3. You must then enable one or more node types to be used with the
|
| 16 |
event system. You can do this by going to admin/node/configure/types
|
| 17 |
and selecting a node type from the list. If the event calendar is
|
| 18 |
installed properly you should see a section called 'Show in event calendar:'
|
| 19 |
with three options below it:
|
| 20 |
|
| 21 |
* None: This content type will not be associated with the events calendar.
|
| 22 |
* All views: This content type will be available for display on all calendar
|
| 23 |
views, including with other events.
|
| 24 |
* Only in views for this type: This content type will only appear in calendar
|
| 25 |
views specific to this type and never with other events.
|
| 26 |
|
| 27 |
'All views' enables the node type will appear on the calendar with all other
|
| 28 |
node types set to 'All views'.
|
| 29 |
'Only in views for this type' will display the type only on its own calendar.
|
| 30 |
Use if you dont want a type appearing with other types.
|
| 31 |
'None' disables a type from appearing on the calendar.
|
| 32 |
|
| 33 |
Once a node type is enabled in this way, event will inject date input fields
|
| 34 |
on that node type's edit form and display them on the calendar views.
|
| 35 |
|
| 36 |
It is recommended that you install the cck module and create event
|
| 37 |
types for this purpose, so you do not have to use core node types
|
| 38 |
for the calendar system.
|
| 39 |
|
| 40 |
Author
|
| 41 |
------
|
| 42 |
|
| 43 |
Kjartan Mannes <kjartan@drupal.org>
|
| 44 |
|
| 45 |
Maintainer
|
| 46 |
----------
|
| 47 |
|
| 48 |
Gerhard Killesreiter <gerhard@killesreiter.de>
|