1.1 --- a/pages/HelpOnEventAggregatorNewEvent Fri May 13 01:36:26 2011 +0200
1.2 +++ b/pages/HelpOnEventAggregatorNewEvent Sat May 28 21:45:53 2011 +0200
1.3 @@ -5,7 +5,7 @@
1.4
1.5 == EventAggregatorNewEvent ==
1.6
1.7 -The !EventAggregatorNewEvent action provides support for creating new events more conveniently than manually editing an event page based on a template. The action can be selected from the actions menu on any page, or it can be invoked by selecting the "New event" link shown when hovering over a day number in an !EventAggregator calendar view.
1.8 +The !EventAggregatorNewEvent action provides support for creating new events more conveniently than manually editing an event page based on a template. The action can be selected from the actions menu on any page, or it can be invoked by selecting a day number in an !EventAggregator calendar view.
1.9
1.10 Upon invoking the action, a form will be displayed requesting values for the following items:
1.11
1.12 @@ -50,7 +50,7 @@
1.13 To manually select the parent page, select the `Show advanced options` button in the form.
1.14 }}}
1.15
1.16 -An event may be assigned a parent page, resulting in the event page being created as a sub-page of this parent page. For a collection of events, a parent page acts as a common container for all the event pages in the collection. For example, a parent page called '''Appointments''' could be defined for the events '''Summer Party''' and '''Winter Party''' with the pages for the events being created as '''Appointments/Summer Party''' and '''Appointments/Winter Party'''. In the calendar, these events would not include '''Appointments''' in their names by default. See the related [[HelpOnEventAggregator#AssigningTemplatesandParentPages|guide to these options]] for more information.
1.17 +An event may be assigned a parent page, resulting in the event page being created as a sub-page of this parent page. For a collection of events, a parent page acts as a common container for all the event pages in the collection. For example, a parent page called '''Appointments''' could be defined for the events '''Summer Party''' and '''Winter Party''' with the pages for the events being created as '''Appointments/Summer Party''' and '''Appointments/Winter Party'''. In the calendar, these events would not include '''Appointments''' in their names by default. See the related [[HelpOnEventAggregator#Assigning_Templates_and_Parent_Pages|guide to these options]] for more information.
1.18
1.19 If the action has been invoked by a link provided by a calendar, the `parent` parameter of the !EventAggregator macro may specify the default parent page for the new event. If no such parameter was used for the calendar, or if no calendar was involved (such as when the action is invoked from the editing menu), no parent page is chosen.
1.20