<add key="PurchaserForceEditFields" value="first_name, last_name, address,
city, state, zipcode, phone, email, username, password" />
These work in the same manner as the keys GuestDispRows, GuestEditRows,
ExistingGuestHideRows, and ForceEditFields, except that they only affect the guest who is set as the
purchaser in the sale. These Purchaser keys can take the same values as the corresponding Guest keys.
Additional configuration can be done in the dynamicControls.xml file. Each field/section in that file now
has a <Required_purch> . . . </Required_purch> setting which can be set to “1” (TRUE) or “0”
(FALSE). Setting this to “1” makes it so that the field will be required if the purchaser edits their guest record.
A new button will appear on either Checkout.aspx or Checkout2.aspx (when using checkout steps) when
you set a purchaser. The button has the default wording of Edit this Purchaser which can be changed in the
markup for the page. This button allows easy access for the purchaser to edit the guest record. Also, if the purchaser
guest record is missing any of the fields set in the PurchaserForceEditFields key, the message configured
with the control asp:label id="lblFieldsRequired" will display. The default wording for this control
is "Please click on Edit Purchaser to edit all the required fields." This can be changed in the markup for the page.
Linked guest log-ins to member log-ins
Guest log-ins are now linked to member log-ins. Add this key to your web.config file: <add
key="GuestLoginAsMember" value="1"/>. Also, make sure MemberFilterDCIs key is set and has
the list of valid DCI's: e.g., <add key="MemberFilterDCIs" value="MEMBERSHIPANNUAL
FAMILY ,MEMBERSHIPANNUAL INDIVIDUAL"/>. You will also need to set <add
key="AllowMultiLogin" value="1" /> in order for this to work.
If a guest has a valid pass defined in MemberFilterDCIs and both GuestLoginAsMember and
AllowMultiLogin are set to "1", then a guest log-in will also work as a member log-in.
If you have both GuestLoginAsMember and AllowMultiLogin set to "1" and <add
key="MemberFilterDCIs" value="" /> (no DCIs specified), then all guests with a valid pass will be
logged in as members. If you populate the MemberFilterDCIs key, then only guests with a valid pass from the
list will be logged in as members.
The guest who is logged in can be different from the member who is logged in, so you can log-out either the guest
or the member.
You can now designate which pass/membership items can be used for a member log-in
Comentarios a estos manuales