| 1 | {* |
| 2 | +--------------------------------------------------------------------+ |
| 3 | | CiviCRM version 4.7 | |
| 4 | +--------------------------------------------------------------------+ |
| 5 | | Copyright CiviCRM LLC (c) 2004-2015 | |
| 6 | +--------------------------------------------------------------------+ |
| 7 | | This file is a part of CiviCRM. | |
| 8 | | | |
| 9 | | CiviCRM is free software; you can copy, modify, and distribute it | |
| 10 | | under the terms of the GNU Affero General Public License | |
| 11 | | Version 3, 19 November 2007 and the CiviCRM Licensing Exception. | |
| 12 | | | |
| 13 | | CiviCRM is distributed in the hope that it will be useful, but | |
| 14 | | WITHOUT ANY WARRANTY; without even the implied warranty of | |
| 15 | | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. | |
| 16 | | See the GNU Affero General Public License for more details. | |
| 17 | | | |
| 18 | | You should have received a copy of the GNU Affero General Public | |
| 19 | | License and the CiviCRM Licensing Exception along | |
| 20 | | with this program; if not, contact CiviCRM LLC | |
| 21 | | at info[AT]civicrm[DOT]org. If you have questions about the | |
| 22 | | GNU Affero General Public License or the licensing of CiviCRM, | |
| 23 | | see the CiviCRM license FAQ at http://civicrm.org/licensing | |
| 24 | +--------------------------------------------------------------------+ |
| 25 | *} |
| 26 | {htxt id="id-event-reg-title"} |
| 27 | {ts}Event Registration{/ts} |
| 28 | {/htxt} |
| 29 | {htxt id="id-event-reg"} |
| 30 | {capture assign=ppUrl}{crmURL p='civicrm/admin/paymentProcessor' q="reset=1"}{/capture} |
| 31 | {ts 1=$ppUrl}If you want to provide an Online Registration page for this event, check the first box below and then complete the fields on this form. You can offer online registration for both Paid and Free events. Paid events require that you have configured a <a href="%1">payment processor</a> for your site.{/ts} |
| 32 | {ts}You may also configure events to require administrative approval prior to participants completing the registration process. To enable this feature you must first enable the Participant Statuses used by the approval work-flow (Administer » CiviEvent » Participant Statuses). Then reload this form and check 'Require participant approval?'.{/ts} |
| 33 | {/htxt} |
| 34 | |
| 35 | {htxt id="event-profile-title"} |
| 36 | {ts}Profile{/ts} |
| 37 | {/htxt} |
| 38 | {htxt id="event-profile"} |
| 39 | <p>{ts}If you want collect additional information during event registration, you will need to configure one or more CiviCRM Profiles - which are collections of standard or custom fields. For event registration, you often want to collect an email address and / or participants' first and last names. You may also need to collect additional information specific to a person's <strong>participation</strong> in an Event. Examples include meal and/or volunteer preferences.{/ts}</p> |
| 40 | <p>{ts}If you haven't already configured custom fields and a profile for this, you can save this screen without selecting a Profile, complete the steps below and then return to <strong>Manage Events</strong> and select your new profile.{/ts} |
| 41 | <ol> |
| 42 | <li>{ts}Create a custom field group which is 'Used for' <strong>Participants</strong>.{/ts}</li> |
| 43 | <li>{ts}Add your field(s) this custom field group.{/ts}</li> |
| 44 | <li>{ts}Create a profile (e.g. 'Participant Information').{/ts}</li> |
| 45 | <li>{ts}Add your custom field(s) to this profile as profile fields.{/ts}</li> |
| 46 | <li>{ts}Return to this screen (<strong>Administer CiviCRM » CiviEvent » Manage Events » Configure » Online Registration</strong>) and select your profile.{/ts}</li> |
| 47 | </ol> |
| 48 | |
| 49 | {capture assign=docLinkCustom}{docURL page="user/organising-your-data/custom-fields" text="custom fields"}{/capture} |
| 50 | {capture assign=docLinkProfile}{docURL page="user/the-user-interface/profiles" text="profiles"}{/capture} |
| 51 | {ts 1=$docLinkCustom 2=$docLinkProfile}Refer to the online documentation for more details on creating %1 and %2.{/ts} |
| 52 | </p> |
| 53 | {/htxt} |
| 54 | |
| 55 | {htxt id="id-link_text-title"} |
| 56 | {ts}Registration Link{/ts} |
| 57 | {/htxt} |
| 58 | {htxt id="id-link_text"} |
| 59 | {ts}Display text for link from Event Information to Event Registration pages (e.g. 'Register Now!').{/ts} |
| 60 | {/htxt} |
| 61 | |
| 62 | {htxt id="id-allow_multiple-title"} |
| 63 | {ts}Multiple Participants{/ts} |
| 64 | {/htxt} |
| 65 | {htxt id="id-allow_multiple"} |
| 66 | <p>{ts}Check this box to allow users to register themselves AND additional participants for an event. When this feature is enabled, users have the option to specify the number of additional participants they are registering for. If this is a paid event, they can select a different event fees for each participant - and will be charged the total of those fees. If a profile is included - they will complete the profile information for each participant.{/ts}</p> |
| 67 | <p>{ts}You can use different profile for the person who is registering than for "Additional Participants". For example, you may want to require an email address from the person entering the registration while not requiring (or even requesting) emails for additional participants (i.e. their "guests").{/ts}</p> |
| 68 | {/htxt} |
| 69 | |
| 70 | {htxt id="id-allow_same_email-title"} |
| 71 | {ts}Allow Shared Email{/ts} |
| 72 | {/htxt} |
| 73 | {htxt id="id-allow_same_email"} |
| 74 | <p>{ts}Check this box to allow a user to register multiple participants using the same email address. Alternatively, if you want additional participants to be registered <strong>without requiring an email address to be entered for each person</strong> - check the "Register multiple participants" option, AND include a profile in this registration form which <strong>includes First Name and Last Name fields</strong>.{/ts}</p> |
| 75 | {/htxt} |
| 76 | |
| 77 | {htxt id="id-dedupe_rule_group_id-title"} |
| 78 | {ts}Duplicate Matching Rule{/ts} |
| 79 | {/htxt} |
| 80 | {htxt id="id-dedupe_rule_group_id"} |
| 81 | <p>{ts}By default, your event will use the Unsupervised duplicate matching rule to match participants in anonymous registrations with existing individuals. You may select another rule to use for this event instead. Make sure that your included profile(s) contain the fields needed by your matching rule.{/ts}</p> |
| 82 | {/htxt} |
| 83 | |
| 84 | {htxt id="id-requires_approval-title"} |
| 85 | {ts}Require Approval{/ts} |
| 86 | {/htxt} |
| 87 | {htxt id="id-requires_approval"} |
| 88 | {ts}Check this box to require administrative approval for all the participants who self-register, prior to being able to complete the registration process. Participants will be placed in 'Awaiting Approval' status. You can review and approve participants from 'Find Participants' - select the 'Participant status - change' task. Approved participants will move to 'Pending from approval' status, and will be sent an email with a link to complete their registration (including paying event fees - if any). {/ts} |
| 89 | {/htxt} |
| 90 | |
| 91 | {htxt id="id-expiration_time-title"} |
| 92 | {ts}Time Limit{/ts} |
| 93 | {/htxt} |
| 94 | {htxt id="id-expiration_time"} |
| 95 | {ts}Time limit <strong>in hours</strong> for confirming/finishing registration by participants with any of the pending statuses. Enter 0 (or leave empty) to disable this feature.{/ts} |
| 96 | {/htxt} |