CONFIGURATION TIPS
==================

Q: But I only want content type X or Y (i.e. Event objects) to be configured as RSVP-aware...

A: To limit which content types the user can easily configure as RSVP-aware, the 
condition_expr for the "allowRSVPs" and "disableRSVPs" actions, could be changed to something 
like (replace 'Event' with the name(s) of your preferred content type below):

 condition_expr="python:not object.restrictedTraverse('@@rsvp-configuration').isRSVPEnabled() and object.portal_type in ('Event',) "


Q: Why can't I remove a referenced PloneFormGen Form Folder object from the Custom Registration form field?

A: The version of ATReferenceBrowserWidget that ships with Plone 3.0.x and 3.1.x does 
not allow users to "Remove reference" for Archetype ReferenceFields where
only one value can be added.  This has been fixed in the trunk of 
ATReferenceBrowserWidget and should be included sometime within the Plone 3.x release cycle.
In the meantime, you need to patch your Plone site's with the following if you 
would like your users to be able to both set AND remove references to custom
PloneFormGen registration forms::

 $ svn diff
 Index: referencebrowser.pt
 ===================================================================
 --- referencebrowser.pt	(revision 9525)
 +++ referencebrowser.pt	(working copy)
 @@ -176,6 +176,13 @@
                       onClick=""
                       i18n:attributes="value label_add;"
                       tal:attributes="onClickstring:javascript:referencebrowser_openBrowser('${startup_directory}','${fieldName}', '${at_url}', '${fieldRealName}')" />
 +              <input type="button"
 +                     class="destructive"
 +                     value="Remove reference"
 +                     onClick=""
 +                     i18n:attributes="value label_remove_reference;"
 +                     tal:condition="not: multiVal"
 +                     tal:attributes="onClick string:javascript:referencebrowser_removeReference('${fieldName}', ${multiVal})" />
            </div>
            <!-- Todo? -->
            <metal:addable metal:use-macro="here/widgets/addable_support/macros/addable"/>


Q. Other tips will be added as needed...