PayPal Express Checkout Smart Payment Buttons Payment Gateway

The PayPal Express Checkout Smart Payment Buttons Payment Gateway will allow your attendees to pay for their event registrations using a credit cards, debit cards, PayPal funds, Venmo, and more.

View quick links for this payment gateway –> 


Need to Buy a Support License for the PayPal Express Checkout Smart Payment Buttons Payment Gateway for Event Espresso 4?
https://eventespresso.com/product/eea-paypal-smart-buttons/

Installation

This payment gateway is a plugin for WordPress and can be installed through your WP dashboard (WP-admin).

Download the latest version of the PayPal Express Checkout Smart Payment Buttons payment gateway for Event Espresso 4 from your Event Espresso account page.

Then login to your WordPress dashboard (WP-admin) and go to Plugins. Next, click on Add New –> Upload and browse to the plugin on your computer. Then select the zip file and begin the upload process. Wait for the plugin to upload and then click on Activate.

Locate your Credentials for PayPal Express Checkout Smart Payment Buttons Payment Gateway

This extension uses the REST API from PayPal which can be found on developer.paypal.com.

Here are the steps to find your credentials for accepting payments:

1) Go to developer.paypal.com
2) Click on the button to Login into Dashboard and sign in using your PayPal.com account credentials
3) You’ll then see the My Apps & Credentials dashboard
4) Scroll down and look for REST API Apps
5) Click on the button to create a new app
6) Type a name for the App (e.g. Event Espresso) and click the button to create the app
7) You’ll now see your Sandbox API credentials. Use the toggle in the top right to click on Live
8) Your Live API credentials will now be visible

You can then copy and paste the Client ID and the Secret into the payment methods page for PayPal Express Checkout Smart Payment Buttons within your WP dashboard and then click on the Update Settings button. You’ll then be ready to accept payments on your site through PayPal Express Checkout Smart Payment Buttons.

Setup and Configuration

Will PayPal Express Checkout Smart Payment Buttons be the only payment method enabled or the only one you offer? Click here to learn how to make it selected by default during the registration checkout.

An account with PayPal is needed to accept payments through the PayPal Express Checkout Smart Payment Buttons payment gateway.

A dedicated SSL certificate is recommended to secure your WordPress website.

Login to your WP-admin (WP Dashboard) and go to Event Espresso –> General Settings –> Payment Methods. Once on the Payment Methods screen, click on PayPal Express Checkout Smart Payment Buttons and click on the button to activate the payment method.


Below are the available fields and explanations for each field.

Name – This is the name of the payment method.
Description – This description is shown during registration checkout.
Admin-Only Name – This is a name of the payment method that will only be shown in the WP Dashboard (WP-admin).
Admin-Only Description – This description is used only in the WP Dashboard (WP-admin).
Debug Mode On? – Enables debugging for this payment method. It should be off (set to no) on a live/production site.
Open by Default? – This sets this payment method to be pre-selected on the registration checkout page.

To give your audience more payment options, you can activate multiple payment methods at the same time. However, if you are offering just one payment option, then we recommend that you set that one payment method to be selected by default during registration checkout. That will simplify the check out process for your attendees.

PayPal REST API App Client ID – This credential is needed to process payments and can be found in your developer.paypal.com account.
PayPal REST API App Secret – This credential is needed to process payments and can be found in your developer.paypal.com account.
Button shape – Choose the shape of the payment buttons.
Button size – Choose the size. Venmo requires the full-width option.
Usable From? – Select where this payment method should be available for use. This payment method cannot process payments through the WP-admin (WP Dashboard).
Order – The value (number) can be used to sort or arrange this payment option. A lower value means that it should appear first during registration checkout.
Update Settings – Click this button after making any changes to your payment method.
Deactivate Payment Method – Click this button to deactivate this payment method.

Usage

The PayPal Express Checkout Smart Payment Buttons payment gateway will let you accept payments through credit cards, debit cards, PayPal funds, Venmo and PayPal Credit. These payment options are dynamically shown based on a buyer’s location so they have flexibility in paying for their event registrations.

This is an onsite payment gateway through a modal window which means that attendees/registrants will remain on your website to complete their payment instead of being taken to a page on PayPal.com and then returned to your website.

Troubleshooting

I configured PayPal Express Checkout Smart Payment Buttons and payments are not being processed
Double-check your credentials to make sure that you are using the live credentials which are for production mode. Also, make sure that there is no extra spacing before or after the credentials in the payment methods page of Event Espresso.

How can I setup a recurring payment or subscription through PayPal Express Checkout Smart Payment Buttons?
Recurring or subscription payments are not currently supported in the PayPal Express Checkout Smart Payment Buttons Payment payment gateway.

When I refund a payment, does it also refund through PayPal.com?
Refunds in Event Espresso 4 are currently a two step process. First, apply the refund through the transactional details screen of Event Espresso in your WP-admin (WP dashboard). Then login to your PayPal merchant account and process the refund.

Is an SSL certificate needed for PayPal Express Checkout Smart Payment Buttons?
A dedicated SSL certificate is recommended if you are accepting payments on your website.

Do I need to be PCI compliant?
Compliance with the Payment Card Industry Data Security Standards (PCI DSS) is required if you are processing, storing, or transmitting credit card data. Event Espresso recommends using a dedicated SSL certificate on your website.

View more information on PCI compliance from PayPal.


Need to Buy a Support License for the PayPal Express Checkout Smart Payment Buttons Payment Gateway for Event Espresso 4?
https://eventespresso.com/product/eea-paypal-smart-buttons/

Posted in | Comments Off on PayPal Express Checkout Smart Payment Buttons Payment Gateway

Authorize.net Accept Payment Gateway

The Authorize.net Accept payment gateway will allow your attendees/registrants to pay for their event registrations with a credit card or debit card. eChecks are also supported.

View quick links for this payment gateway –>


Need to Buy a Support License for the Authorize.net Accept Payment Gateway for Event Espresso 4?
https://eventespresso.com/product/eea-authorizenet-accept/

Installation

This add-on requires a current version of Event Espresso.

This payment gateway is a plugin for WordPress and can be installed through your WP dashboard (WP-admin).

Download the latest version of the Authorize.net Accept payment gateway for Event Espresso 4 from your Event Espresso account.

Then login to your WordPress dashboard (WP-admin) and go to Plugins. Next, click on Add New –> Upload and browse to the plugin on your computer. Then select the zip file and begin the upload process. Wait for the plugin to upload and then click on Activate.

Locate your Credentials for Authorize.net Accept

Your credentials for Authorize.net Accept can be found in your Authorize.net merchant account. It uses your API login and Transaction key. Here are the steps to find your credentials for Authorize.net Accept.

You can then add your API login and Transaction key through your WordPress dashboard (WP-admin) –> Event Espresso –> Payment Methods –> Authorize.net Accept. Be sure to save changes.

Afterward, enable the Transaction reporting option through your Authorize.net account.

Want to test Authorize.net Accept before accepting payments in live / production mode?

You can enable debug mode through your WordPress dashboard (WP-admin) –> Event Espresso –> Payment Methods –> Authorize.net Accept. Be sure to save changes.

After testing, you can turn debug mode off and save changes. This will allow you to accept live payments.

Will Authorize.net Accept be the only payment method enabled or the only one you offer? Click here to learn how to make it selected by default during the registration checkout.

Setup and Configuration

A Authorize.net account is needed to accept payments via Authorize.net Accept. Need an account? Sign-up for a Authorize.net merchant account to get started.

A dedicated SSL certificate is required to accept payments through Authorize.net Accept.

Login to your WP-admin (WP Dashboard) and go to Event Espresso –> General Settings –> Payment Methods. Once on the Payment Methods screen, click on Authorize.net Accept and click on the button to activate the payment method.

Below are the available fields and explanations for each field.

Name – This is the name of the payment method.
Description – This description is shown during registration checkout.
Admin-Only Name – This is a name of the payment method that will only be shown in the WP Dashboard (WP-admin).
Admin-Only Description – This description is used only in the WP Dashboard (WP-admin).
Debug Mode On? – Enables debugging for this payment method. It should be off (set to no) on a live/production site.
Open by Default? – This sets this payment method to be pre-selected on the registration checkout page.

To give your audience more payment options, you can activate multiple payment methods at the same time. However, if you are offering just one payment option, then we recommend that you set that one payment method to be selected by default during registration checkout. That will simplify the check out process for your attendees.

Authorize.net API login ID – A credential for accepting payments.
Authorize.net Transaction key – A credential for accepting payments.
Billing address – Enable to collect a registrant’s billing address.
Shipping address – Enable to collect a registrant’s shipping address.
Button URL – This is the URL to the image that will be used during the payment process of registration checkout.
Alternative Button URL: https://ee-screenshots.s3.amazonaws.com/2015/07/pay-by-credit-card.png
Pay by bank card
Usable From? – Select where this payment method should be available for use. This payment method cannot process payments through the WP-admin (WP Dashboard).
PMD Order – The value (number) can be used to sort or arrange this payment option. A lower value means that it should appear first during registration checkout.
Update Settings – Click this button after making any changes to your payment method.
Deactivate Payment Method – Click this button to deactivate this payment method.

Usage

The Authorize.net Accept payment gateway will let you accept payments via major credit or debit cards. eChecks are also supported if you have the eCheck service enabled on your Authorize.net merchant account.

This integration uses the Hosted option with Authorize.net through an iframe. This means that a guest will remain on your website while they are paying and their payment details will be transferred to Authorize.net securely through an iframe form.

An account with Authorize.net is needed to accept payments via Authorize.net Accept and an SSL certificate is required.

Troubleshooting

I configured Authorize.net Accept and payments are not being processed. Can you help?
Double-check your credentials to make sure that you are using the API Login ID and Transaction key. Also, make sure that there is no extra spacing before or after the credentials in the payment methods page of Event Espresso.

I see a message in the payment details about the payment being success but not being verified. How do I resolve this?
You can correct this issue by enabling the Transaction Reporting API through your Authorize.net account.

How can I setup a recurring payment or subscription through Authorize.net Accept?
Recurring or subscription payments are not currently supported in the Authorize.net Accept payment gateway.

When I refund a payment, does it also refund through Authorize.net Accept?
Refunds in Event Espresso 4 are currently a two step process. First, apply the refund through the transactional details screen of Event Espresso in your WP-admin (WP dashboard). Then login to your Authorize.net account and process the refund.

Is an SSL certificate needed for Authorize.net Accept?
A dedicated SSL certificate is required to use the Authorize.net Accept payment gateway.

Do I need to be PCI compliant?
Compliance with the Payment Card Industry Data Security Standards (PCI DSS) is required if you are processing, storing, or transmitting credit card data. Event Espresso helps by using Authorize.net Accept’s iframe option for payment processing.

View more information on PCI compliance from Authorize.net.

Customizations

Our support team cannot write custom coding for you. Below are some examples on customizing this payment gateway.
  • This payment method includes an option to collect an attendee’s billing address and shipping address during registration checkout. It is available in the settings page for Authorize.net Accept on your WordPress website.



Need to Buy a Support License for the Authorize.net Accept Payment Gateway for Event Espresso 4?
https://eventespresso.com/product/eea-authorizenet-accept/

Posted in | Comments Off on Authorize.net Accept Payment Gateway

Accept donations alongside event registrations with Event Espresso

Donations can help your organization reach its fundraising goals by allowing contributions from guest’s that are attending as well as guests that cannot make it to an event.

For example, let’s say that you are hosting a dinner to benefit your favorite local charity. The cost of the dinner is $50 per guest, and you have spots for up to 45 guests. By introducing some fixed-price donation options, you can further raise funds so you’ll have these pricing options.

– Registration for dinner: $50 (required)
– Donation for $50
– Donation for $100
– Donation for $250

With the options above, a guest that is attending can donate in addition to choosing the required registration option.

Variable donation options are not yet supported, and you can create fixed-price options. Vote for this feature here.

There are two ways to handle donations in Event Espresso.

1) The donations can be created as extra pricing options through the event editor and be connected to their own date time, so they don’t affect the limit of the dinner

2) You can create a separate event that handles registrations for donations only. Then you can include a link to the donation-only event in the original event’s description. You can even create a custom registration approved email that asks for donations after a guest has registered.

Posted in | Comments Off on Accept donations alongside event registrations with Event Espresso

How to get professional conference badges with QR codes

You can design custom name badges for your upcoming event and get them shipped or print them yourself. This guide shows how to get attendee data from Event Espresso and import that data into an online badge creation tool available from conferencebadge.com. These badges can even include QR-codified data so you can scan the badges with Event Espresso-compatible mobile apps to check-in people at the event’s entrance!

Get the attendee data from Event Espresso

  1. Go to Event Espresso > Events and click the link to view the registrations for the event
  2. Click the CSV Report button and download the generated report to your computer
  3. Open the CSV report in a spreadsheet application
  4. Delete the columns that contain data that will not be displayed on the name badges
  5. Export the spreadsheet to an Excel file

Import the attendee data and design your badge

  1. Go to conferencebadge.com and open an account (or log in)
  2. Click + New Event from Excel and upload your spreadsheet file
  3. Match your spreadsheet columns with your attendee info
  4. Choose a product, badge size, and theme
  5. Use the badge builder to add your logo, static text, and attendee data
  6. If you’re planning on using the ticketing apps you can QR Codify the Unique Registration code field
  7. Preview and Checkout
Need more ideas and tips for designing your event’s name badges? Check out this name badge design guide.

Posted in | Comments Off on How to get professional conference badges with QR codes

2017 Changelog Archive

November 29, 2017

Event Espresso 4.9.53.p

Bug fixes:

  • Fix undefined variable in EED_Core_Rest_Api::maybe_notify_of_basic_auth_removal()
  • Fix Catchable fatal error:
    Argument 2 passed to EED_Messages::payment() must be an instance of EE_Payment, null given in EED_Messages.module.php on line 458
  • Fix broken EE_Post_Content_Field and EE_Simple_HTML_Field sanitization
  • Add core filter for Event Customization app to hook into

November 28, 2017

iPay88 Payment Method 1.0.2.p

Enhancements:

  • Add support for Indonesia
  • Filter order description method

November 21, 2017

Event Espresso 4.9.52.p

Bug fixes:

  • Fix change timezone from UTC persistent notice
  • Fix Datetime offset tool redirect on sites with subdomains
  • Fix question editor not saving changes
  • Improve modal centering for small screens

November 16, 2017

Event Espresso 4.9.51.p

Bug fixes:

  • Ensure nag notice message is set when redisplaying existing notice
  • Don’t show the payment method was automatically deactivated messaging to subscribers
  • Fix possible runaway ee_transient_schedule and ee_ssn_* and ee_shc_* transients
  • Make question type categories more accessible
  • Fix argument 1 passed to EEH_Line_Item::delete_all_child_items() must be an instance of EE_Line_Item, null given

Update

  • Improve EE_Registrations_incoming_data so that convert_data_for_persistent_storage receives (and validates) IDs instead of objects

November 8, 2017

Event Espresso 4.9.50.p

Bug fixes:

  • Fix issue where some expired session transients are not deleted
  • Fix unclosed anchor tag in event editor for duplicator button link
  • Fix Fatal Error:
    Call to a member function execute() on boolean in EED_Messages.module.php
  • PayPal Express: Pass Line Item details in DoExpressCheckoutPayment API call
  • Improve session expiry error messages
  • Add extra check for compatibility before migrating tables to utf8mb4
  • Add warning before resetting DB tables from EE Maintenance page

Enhancements:

  • Update messaging shown in registration checkout if an event is full and a guest is trying to pay
  • Change use of esc_sql() in
    EEH_Event_Query::posts_where_sql_for_event_category_slug()
    to use $wpdb-prepare() instead
  • Improve Datetime Offset tool
  • When clicking valid shortcode, add it to the related field (newsletter composing)
  • Update UXIP link to use HTTPS

October 19, 2017

QuickBooks payment method 1.0.2.p
Updates:

  • Add trailing slash on root URL used with redirect_uri

October 18, 2017

Event Espresso 4.9.49.p

Updates:

  • Add [RECIPIENT_EDIT_REGISTRATION_LINK] shortcode to available newsletter template shortcodes
  • Fix auto-demotion of registrations to Wait List

October 13, 2017

Event Espresso 4.9.48.p

Bug fixes:

  • Remove spaces between HTML tags when creating PDFs through DOMPDF
  • Fix REST API unit test failures and endpoint query filtering due to changes in WordPress 4.9
  • Check for mb_strcut before attempting to use it
  • Error proof method in EE_Capabilities where the assumption is made that a site has any of the default roles
  • Fix messages system bulk option ‘Generate and send’ not sending messages
  • Revisit – Improve display of sub line items on Payment Options step
  • Fix duplicate cache keys being generated in
    PostRelatedCacheManager::clearPostRelatedCacheOnUpdate()

Enhancements:

  • Add a shortcode for the TXN ID returned from the gateway to the payment received messages

October 11, 2017

Event Espresso 4.9.47.p

Bug fixes:

  • Fix opening and closing div mismatch on SPCO return to Payment options page
  • Restore setting transactions to Abandoned transaction status
  • Fix form help text container appearing in form markup despite there being no help text
  • Don’t load trashed registrations when processing messages
  • Fix forms system output before multiple choice checkbox html
  • Fix issue where abandoned registrations keep reserved tickets
  • Fix bug with the default generation of EE_Message_Addressee objects for address context within EE_message_type
  • Fix issue where email field is blank after saving invalid email address in the admin
  • Fix issue where ticket/datetime cloner copies over the ticket’s/datetime’s reserved count
  • Fix issue where bullhorn action does not track batch messages
  • Fix permanent delete events action
  • Fix usage of deprecated WP_User::_init_caps in tests (and code)
  • Fix single context message generation for messages
  • Fix failing test case in EE_Registration_Processor_Test
  • Fix generating preview for registration type messages creating entries in the message activity list table
  • Fix transaction event revenue report sub-query
  • Convert all uses of do_action() to do_action_ref_array() where arrays of objects are passed as the first parameter
  • Include proper default where conditions for transaction query
  • Fix failing unit test due to Daylight Savings Time
  • Use prefixed clearfix html class for the [ESPRESSO_EVENTS] shortcode’s pagination element
  • PayPal Express order description: Use mb_strcut() instead of substr()
  • Fix HTML entities shown in CSV column headers
  • Move BN field in PayPal Express to the DoExpressCheckout parameter
  • Fix issue with filtered CSV reports where some registrations are replaced with another registration from the same transaction
  • Fix support link in plugin description

Enhancements:

  • Configure PSR-4 Autoloader before bootstrapping Event Espresso
  • Add ability to make admin notices dismissible
  • Add new updateStatusBasedOnTotalPaid() method and call when copying registrations
  • Create new Context DTO class as a standardized way of passing along contextual knowledge when performing an action
  • Add ContextChecker Class
  • Tweak EE_Attendee::full_name() to only add space between first and last names if both exist
  • Add filter for where conditions on query for question groups for the question group meta boxes in the event editor
  • Add filter on default value for EE_Base_Class::get_extra_meta so that plugins can override what the default is for a meta key
  • Improve after_registration method on EE_Register_Addons so that it is delayed a bit from being called until after client code has a chance to deregister an add-on
  • Display form-wide errors

Updates to core to add support for waitlist add-on:

  • Add getter for $iframe property to DisplayTicketSelector
  • Fix error on finalizing registration when the visit should automatically demote all pending registrations in a group to the waitlist from pending payment
  • Fix form generation when multiple FormHandlers are on the same page
  • Improve Checkout response for Wait List registrants

Merged pull requests from Github:

September 11, 2017

Event Espresso 4.9.46.p

Bug fixes:

  • Use Event Espresso version when registering admin stylesheets
  • Fix incorrect count returned by EE_Event::spaces_remaining() when there are two tickets attached to one datetime that has a registration limit
  • Display all ticket selector content when retrieved via AJAX requests
  • Fix issue where icon for check-in status not displaying correctly for toggled check-ins
  • Fix HTML/CSS class change on registration form questions
  • Fix Fatal error that occurs when deactivating Payment Method addons
  • Fix issue where simple ticket selector ignores minimum ticket capability
  • Add LoaderFactory
  • Fix Fatal error: Function name must be a string (when server has PHP 5.3)
  • Fix Reset Capabilities tool so it re-adds ee_payment_method_{pm_name} capabilities
  • Add Cache control parameter to LoaderDecoratorInterface
  • Fix issue where JSON linked data schema formatting overrides date and time formats used elsewhere
  • Don’t unset non-object values when resetting EE_Registry
  • Fix Front end Maintenance Mode so site admins can access events on the front end
  • Fix Bulk actions: ‘Set Registrations to Not Approved’ action
  • Fix [ESPRESSO_EVENT_ATTENDEES] shortcode
  • Don’t set MIME version in email headers
  • Fix EE add-on menu depending on capabilities for display not displaying after initial activation of add-on adding those capabilities
  • Fix missing bulk actions on Filtered by Event check-in list table view
  • Don’t grant meta capabilities (e.g. ee_edit_event) to a role
  • Fix exception thrown when using the contacts ‘Move to trash’ bulk action
  • Fix <code> tags displayed in messages settings
  • Fix issue where some shortcode assets are not loaded on private pages/posts
  • Only set the timezone on the model from the model object during
    EEM_Base::instantiate_from_array_or_object for EEM_Event
  • Fix EE_Line_Item::recalculate_total_including_taxes() for cloned line items generated by
    EE_Line_Item_Filter_Processor::clone_and_reset_line_item_tree()
  • EE4 REST API: Avoid notice thrown when using [ESPRESSO_EVENT_ATTENDEES] in an events description
  • Fix Integration Test expectations in phpunit test cases for REST endpoints

Enhancements:

  • Allow authenticated users to insert data using the REST API
  • Optimize/speed up creation of EE4 model objects
  • Add a [VENUE_META] shortcode to the message templates
  • Move checkin status constants to EE_Checkin class
  • Extract all WP_Admin_Bar related logic from EE_System into new application and domain services
  • Inject the new Loader class (and other dependencies) into EE_System and use for loading classes
  • Instantiate ShortcodesManager using LoaderFactory::getShared()
  • Add ModelFieldFactory class
  • Refactor EE_Request_Handler::is_set() and get() to drill down and find request parameters nested deeper than the top level of the request parameter array
  • Add user interface toggle for turning on or off messages contexts
  • Add new messages shortcode for generating the url to the venue details page
  • Display friendly error message when there is no active payment method in
    EE_SPCO_Reg_Step_Payment_Options::_get_selected_method_of_payment
  • Add filter hook to question groups query in
    EE_SPCO_Reg_Step_Attendee_Information::_registrations_reg_form
  • Add filter hook to query getting questions for a question group found in
    EE_SPCO_Reg_Step_Attendee_Information::_question_group_reg_form
  • Add cc: field to email message templates
  • Add helper method to EEH_URL for removing specified query parameters from the
    current_url result
  • Modify EE_Register_Shortcode to handle registering shortcodes in the newer shortcode system
  • Add more information to the single check in record view
  • Add notice warning about upcoming changes impacting those using a UTC offset for datetimes
  • Add link to front end reg_url_link from the transactions admin list page
  • Automatically delete any related esp_extra_meta records when an EE_Entity is permanently deleted
  • Simplify EEM_Base::delete_permanently to actually know which model objects are getting deleted
  • Add “step” attribute to EE_Number_Input_Display_Strategy and do validation of incoming values
  • Convert EEM_Change_Log::Log_Type field to a Text Field so there is more flexibility for the types that can be used

September 6, 2017

Payment Methods Pro 1.0.1.p
Enhancments:

  • Change hook used to check if MER is activated and de-activate
  • Don’t use currency payment method model

August 24, 2017

Espresso Grid View 1.2.4.p
Enhancements:

  • Allow viewing event info on mobile devices
  • Allow add-on to load different custom templates

August 22, 2017

Espresso Calendar 3.2.11.p
Enhancements:

  • Filter the registration button html to allow for custom register now buttons
  • Allow multiple categories at the same time with a single ESPRESSO_CALENDAR shortcode
  • Allow the use of parent categories within the calendar

August 3, 2017

Event Espresso Ticket Scanning add-on 1.0.11.p

Bugfixes:

  • Fix incorrect capability check used for Barcode Scanner functionality
  • Include private events in scanner ui event drop down

July 26, 2017

Event Espresso 4.9.45.p

Bug fixes:

  • Don’t return early from save() for unchanged objects with non-int IDs, and fix creation of Status objects in unit tests
  • Remove unused bulk actions dropdown menu from default message templates admin page
  • Fix issue where duplicating an event does not copy over Featured image, page template selection, custom message templates
  • Fix phpunit tests running on phpunit 6.1+ for PHP7 and PHP7.1 in
    EE_Register_Capabilities_Test
  • Use constant for DOMPDF_DEFAULT_PAPER_SIZE instead of hardcoded value
  • Fix issue where select Ajax Mode REST Input doesn’t actually accept normal query params
  • Fix WP_Query args stripped out of EventListQuery

Enhancements:

  • Improve to EE_Base_Class::save()’s use of $_has_changes property
  • Improve Custom_Messages_Template_List_Table by extending
    Messages_Template_List_Table

July 19, 2017

EE4 Promotions 1.0.11.p

  • Don’t run additional logic in main addon class used for addon registration
  • Add [PROMOTIONS_USED] shortcode to transaction based message shortcodes
  • Filter the event names within the ‘Promotion applies to…’ metabox
  • Update the [ESPRESSO_PROMOTIONS] shortcode description text

July 17, 2017

Event Espresso 4.9.44.p

Bug fixes:

  • Fix issue where event duplicator duplicates an event’s datetime ticket reserved count
  • Fix issue where Country Settings page is giving no feedback when changing the settings
  • Fix issue where localized data objects are output twice
  • Fix Uncaught ReferenceError: ee_dismiss is not defined JavaScript error when dismissing an EE admin notification
  • Allow archived tickets (that have no registrations) to be deleted
  • Fix PHP notices that occur when saving settings on Event Espresso > Events > Templates
  • Fix dependencies for PostRelatedCacheManager
  • Fix usage of venue-related strings when calling
    EE_Config::register_route()
  • Fix undeclared variable in
    EE_Message_Resource_Manager::ensure_messengers_are_active()
  • Fix issue where the CSV file gets removed from the server before Chrome can download the file
  • Fix issue where clicking the “Move to Trash” link on an auto draft event/venue does not remove the post

Enhancements:

  • Create interfaces for “tagging” classes as singletons with a reset() method, and for classes that do not store blog or request specific state
  • Rename ConstantsAbstract to DomainBase and add Domain class to core
  • Create LoaderFactory
  • Add new actions and filter hooks
  • Refactor some methods that calculate tickets sold and/or remaining
  • Refactor the dropdown filter that displays registration statuses on the Registrations Admin list table
  • Update Dependency Map
  • Add filter on Extend_Registration_Form_Admin::_email_validation_settings_form for section proper subsections so the output can be modified
  • Add new action in duplicate event logic to hook in when other related items are being duplicated
  • Add timestamp display to registration checkins list table
  • Add clarification to the Reset/Delete Data page to inform that Event Category Terms will not be deleted

June 28, 2017

Event Espresso 4.9.43.p

Bug fixes:

  • Enqueue espresso_default.css when EE upcoming events widget is displayed
  • Avoid: openssl_cipher_iv_length() [function.openssl-cipher-iv-length]: Unknown cipher algorithm warnings
  • Avoid conflicts with plugins that optimize script loading
  • Load deprecated EE_Event_List_Query class for backwards compatibility
  • Fix issue where displayed Subtotal of ticket price gets rounded to the nearest dollar in the admin
  • Make sure EventEspresso\core\services\assets\Registry is loaded as cached so it gets set on the AssetsRegistry property in EE_Registry
  • Improve default experience for Decaf messages where date time name and description shortcodes are used
  • Fix Multi-status summary message type so it sends messages only if there are multiple registration statuses
  • Fix “Move to Trash” link within any EE CPT editor (event, venue, person, attendee/contact)
  • Make admin registration list more responsive for small screens
  • Don’t cache ticket selector and attendee shortcodes
  • fix TableManager::dropTables() where multiple EE models use the same EE table

Enhancements:

  • Improve display of sub line items on Payment Options step
  • Add filter for AdminOptionsSettings generated form sections
  • Add filter hook to allow changing the registrations search query
  • Add a Select Timezone in the Timezone admin alert

June 15, 2017

Braintree 1.0.6
Bug fixes and Enhancements:

  • Don’t run additional logic in main addon class used for addon registration
  • Update Braintree SDK and add additional filter hooks
  • Remove the accepted message

June 14, 2017

Event Espresso 4.9.42.p

Bug fixes and Enhancements:

  • Fix issue where returning from an off-site gateway results in a blank screen on servers that don’t have output_buffering set to On
  • Fix undefined index/invalid argument warning from Messages class when messages are set to send on same request
  • Allow custom message templates to be used if all events in the cart are set to use the same custom message template

June 11, 2017

Event Espresso 4.9.41.p

Bug fixes:

  • Fix missing space between attributes and missing attribute closing bracket in event editor inputs
  • Fix broken pagination in ESPRESSO_EVENTS shortcode output

Updates:

  • Remove link to sign up for Mijireh account
  • Deprecate EEM_Currency_Payment_Method and EE_Currency_Payment_Method, and no longer insert rows into esp_currency_payment_method when activating new payment methods or during the 4.6 migration.

June 8, 2017

Event Espresso 4.9.40.p

Bug fixes:

  • Paypal Express – treat SuccessWithWarning as success, so duplicate requests are treated as success
  • Fix Notice: Trying to get property of non-object in
    core/helpers/EEH_Event_View.helper.php on line 59
  • Fix timeout on Maintenance page system info
  • Fix issues with EE_Config
  • Add fix for themes that don’t call get_header()
  • Don’t cache Ticket Selector shortcode’s output
  • Fix PHP Fatal error: Uncaught Error: Class EE_Event_List_Query not found

Updates:

  • Update credits tab
  • Initial file cleanup for event editor classes
  • Simplify enqueueing of assets in EE_System and other core classes

May 30, 2017

Event Espresso 4.9.39.p

Bug fixes:

  • Fix issue where success notices are not showing for triggering resend of messages
  • Remove usage of mcrypt as it has been deprecated in PHP7.1
  • Bump the_content filter priorities back up to what they were originally
  • Fix open and closing div tag mismatch in the Ticket Selector that occurs with Expired tickets
  • Get current form step and make sure it is displayable before attempting to display progress steps
  • If event has default reg status of Not Approved, then don’t display info on it, unless there are registrations for it that are returning to pay
  • Add is_object() check in LooseCollection::add() method
  • Add new state form: Use EE_Div_Per_Section_Layout() instead of EE_No_Layout() so that validation errors appear in the correct location
  • Fix Batch message button’s selected registration count
  • Fix issue where Registration Multi-status Summary messages do not get triggered
  • Fix backticks found in links for Custom Message Templates
  • Fix resetting of EE_Error notices in Extend_General_Settings_Admin_Page
  • Fix the messages [QUESTION] shortcode value returned now being wrapped in <p> tags
  • Add check for iconv() before converting characters in Authnet AIM fields
  • When no response is received from AIM, give a more helpful message
  • Fix array to string conversion EE_Text_Normalization.strategy.php on line 38 when manually applying a payment/refund
  • Fix the invoice payment method default ‘Confirmation Text’ string
  • Set PayPal Pro’s order description field’s limit to 127 characters

Enhancements:

  • Don’t instantiate models just to map meta caps
  • Add Benchmark class for testing loading and execution times
  • Don’t use post shortcodes array for tracking but instead load resources dynamically
  • Allow Closures for dependency loaders and allow aliases for specific classes
  • Add Command Factory
  • Add ability to execute Commands from within CommandHandlers
  • Add new shortcode [GOOGLE_MAPS_URL] that will return the url to the Google map
  • Add show_title parameter for the [ESPRESSO_EVENTS] shortcode
  • Registrations CSV – Force phone number to display as text within Excel
  • EE4 data deletion: Add clarification to explain what it does with add-ons

May 2, 2017

Event Espresso 4.9.38.p

Bug fixes:

  • Fix conditional to avoid Cannot use object of type WP_Error as array
  • Restore SPCO form validation message box
  • Change database field limits to allow more decimal places for line item and transaction totals
  • In EE_Transaction primary_registration method get all primary registrations and look for one that isn’t canceled, or just return first item found
  • Fix behaviour of add-on message types so that active state is preserved across deactivations/de-registration and reactivation/registration of the add-on
  • Add tooltip to Rsrvd field
  • Fix PHP notice for EE4 Decaf Plugin Update Engine
  • Add check for slug field for Plugin Update Engine client
  • Fix broken inputs in mobile Datetime and Ticket editor
  • REST API: Filter out shortcodes within the Event Description field
  • Make sure EEH_Activation::delete_all_espresso_tables_and_data only lists tables once in the assembled drop tables expression
  • Fix addon activation in EE_Register_Addon not properly setting the activation indicator option

Enhancements:

  • Create Integer Input class and corresponding number display strategy
  • Create Loading System with controllable built-in caching
  • Implement new constants abstract that can be utilized by core and add-ons for their own Constants file
  • Add option to set a default value for the Maximum number of tickets allowed per order for this event field
  • Add improvements to Plugin Update Engine client to make it more resilient
  • Update various content on Event Espresso admin pages
  • Use the_content filter on EE_Post_Content_Field get_pretty method
  • REST API: Change the no-SSL message

May 1, 2017

Stripe 1.0.15
Bug fixes and Enhancements:

  • Don’t run additional logic in main addon class used for addon registration
  • Add filter hooks
  • Remove the accepted message
  • Fix issue where payment amount is not displayed
  • Add filter for the $stripe_data array used when making a Stripe charge
  • Add data-locale parameter so Stripe will use the customer’s language
  • Change order of credential fields

Infusionsoft 2.1.5
Bug fixes and Enhancements:

  • Don’t run additional logic in main addon class used for addon registration
  • Handle exceptions which might be thrown when syncing
  • Fix failing unit tests

Ticketing 1.0.5
Bug fixes and Enhancements:

  • Don’t run additional logic in main addon class used for addon registration
  • Fix issue where the ticket notice is not generated when the send on same request option is enabled for the messages system and only the primary registrant context is enabled
  • Change default Ticket Notice templates to use [TXN_TICKETS_APPROVED_URL] short code
  • Add error proofing for `EE_Ticketing::_get_ticket_url()`
  • Use home url instead of site url for ticket link urls

April 12, 2017

Event Espresso 4.9.37.p

Bug fixes:

  • Fix hook names where different action hooks have the same names
  • Use EE plugin version instead of WP version for script version number added to the asset’s URL as a query string for cache busting purposes
  • Fix multiple payments methods shown when Payment Methods Pro is de-activated
  • Fix EE4 REST API not reporting check-in status when tickets are trashed
  • Fix issue where un-required and un-selected State registration form fields throw validation error
  • Fix failing unit test for EE_Form_Section_Proper_Test::test_submitted_values
  • Fix undefined variable: current_db_state in migration_options_from_ee4.template.php on line 32

Enhancements:

  • Add new method to EEM_Event for getting active and upcoming events
  • Add new filter hooks in the Help > Shortcodes tab content

April 3, 2017

Event Espresso 4.9.36.p

Bug fixes:

  • Revert: Configure PSR-4 Autoloader before bootstrapping EE

March 30, 2017

Event Espresso 4.9.35.p

Bug fixes:

  • Fix blank State field when returning to edit information on attendee information step
  • Fix issue where payments cannot be deleted when they are attached to registrations
  • Fix ticket selector when Maximum number of tickets allowed per order equals 1 and WP User integration restricts tickets
  • Fix issue where ticket reservations aren’t cleared when the Multi Event Registration cart is abandoned
  • Fix conditional that breaks message queueing in PHP5.6+
  • Fix “Text Domain” in plugin header
  • Fix issue where [PAYMENT_GATEWAY] shortcode always returns “Invoice”
  • Add better REST API check-in endpoint responses
  • Check if the URL includes a scheme, if not append ‘http://’ to Venue Editor’s Event URL field

Enhancements:

  • Configure PSR-4 Autoloader before bootstrapping EE
  • Add new hooks to Single Page CheckOut for use in Wait List add-on
  • Add FormHtmlParser class for parsing a form section’s rendered HTML

March 16, 2017

Event Espresso 4.9.34.p

Bug fixes:

  • Fix issue where canceling a PayPal Express payment from a revisit leads to a blank registration screen
  • Fix ticket selector output when ticket selector row content is filtered
  • Fix front end date picker input not loading CSS (Github pull request)
  • Don’t send emojis in Authorize.net AIM requests

Enhancement:

  • Add REST API site_info to provide basic auth data required by mobile apps

March 10, 2017

Event Espresso 4.9.33.p

Bug fix:

  • Fix Reg_code not getting set

March 9, 2017

Event Espresso 4.9.32.p

Bug fixes:

  • Fix answer cache id when processing attendee info during spco return visit
  • Add button to Maintenance > Reset page: Reset Ticket and Datetime Reserved Counts
  • Reinstate AHEE__EE_Cron_Tasks__finalize_abandoned_transactions__abandoned_transaction action hook
  • Switch registration status to “Cancelled” when registration is moved to Trash bin
  • Restore the change in ticket selector table so that if no free tickets require selection, no selector is displayed
  • In REST API schema response, ensure immutable properties (fields) on a model are correctly represented by the readonly flag.
  • Remove warnings about Basic Auth’s removal
  • Make bundled basic auth not interfere with oAuth server
  • Fix HTML IDs in Payment method settings admin pages so JavaScript validation works with Payment Methods Pro add-on
  • Mijireh payment method: When checking whether a transaction is paid via Mijireh, check all its pending Mijireh payments, not just the most recent one
  • Add error proofing to EEH_Schema.helper.php

New features and Enhancements:

  • Embed Upcoming Event List for displaying and event list on other websites
  • Set txn property on EE_Messages_Registrations_incoming_data if all the registrations that are sent in are for the same transaction
  • Build in support for conditional type shortcodes in the Messages Shortcode parser
  • Add action for before an addon is de-registered using EE_Register_Addon and after an addon has been de-registered using EE_Register_Addon
  • eejs-api: Make sure the library authorizes with cookie if available
  • Separate “fetch” behaviour for the vue model mixin from the “add” behaviour (among other important changes)
  • Make sure in the schema that the value for default follows the same pattern as what is used for the field value
  • Allow passing basic auth authentication data in querystring
  • Add another action hook when forms are constructed
  • Add a button on the system information page to download an html file of system information

February 20, 2017

Event Espresso 4.9.31.p

Bug fixes:

  • Don’t set radio button value to checked when ticket selector has more than one ticket option
  • Fix issue where a valid ticket selection throws “A valid ticket could not be retrieved for the event.” error
  • Delay call to EventEspresso\core\services\assets\Registry::wp_localize_scripts until latest possible moment to allow for late data registration
  • Add improvements to the registration list table and checkin list table’s sorting and link titles, new filter hook
  • Fix issue where migrations and batch jobs sometimes do not report errors
  • Allow changing the Phone Number system question’s question type to “US Phone”
  • Remove warnings when checking for database indexes on non-existent tables
  • Fix issue where the extra slash in batch CSV reporting assets caused JavaScript to not load on some servers
  • Fix the_latest_event_date() helper method

Enhancements

  • Merge pull request 178 – new spans with CSS classes added to datetime markup
  • Merge pull request 206 – new action hook
  • Include defaults for model fields with json-schema
  • Use a constant for max number of characters that can be indexed in utf8mb4
  • Fix action in wrong location within locate_template()
  • Add filter to allow changing the data used to generate ICS files

New Feature:

  • Allow managing older message activity data

February 16, 2017

Espresso Calendar 3.2.8.p

Bugfixes:

  • Add sanitization for shortcode attributes
  • Show featured image thumbnails even on the smallest screens
  • Use version_compare for Database Migration Scripts version comparisons in Calendar

Enhancements:

  • Add support for embeddable Calendar in an iframe
  • Add filter hook to allow filtering the display of the event’s start/end time in the calendar
  • Add ID anchor to the Category legend, Venue Select, and Category select that appear above the calendar
  • Add filter hooks around the events permalink output

February 6, 2017

Event Espresso 4.9.30.p
Bug fixes:

  • Add sanitization for shortcode attributes that don’t get sanitized/whitelisted in EEH_Event_Query
  • Fix short code month parameter for the [ESPRESSO_EVENTS] short code
  • PHP 7 compatibility: Change the usage of clone so its used properly
  • PHP 7 compatibility: Make sure declaring magic method as a static method
  • Fix issue with template pack api
  • Fix forms system to allow a default null value for dropdown question fields
  • Allow Upcoming Events Widget to also show “Sold Out” upcoming events
  • Add a cron task to delete gateway logs older than a week
  • Fix issue where All Registrations Report times out with many, many, many registrations
  • Ensure all db indexes smaller than 191 characters
  • Fix issue where payment methods that do not support the current currency are available within Single Page CheckOut
  • Remove the “Braintree free 50k” plug from the about page (promotion has ended)

January 31, 2017

Event Espresso 4.9.29.p
Bug fixes:

  • Fix issue where shortcode for the Registration Cancelled page could not be configured properly
  • Fix issue where “please select a datetime” text is being displayed
  • Fix end of month bug in Event list table month filter selector
  • Add backwards compatibility for older versions of WordPress to avoid Fatal error: Call to undefined function EventEspresso\core\services\assets\rest_url()

January 27, 2017

Event Espresso 4.9.28.p
Bug fixes:

  • Fix blank ticket selector on backend admin new registration page

January 26, 2017

Event Espresso 4.9.27.p
Bug fixes:

  • Fix CSS for registration form labels for small screens
  • PHP7.1 – Fix ‘Warning: Illegal string offset ‘xxx’ in /event-espresso-core-reg/core/admin/EE_Admin_List_Table.core.php on line 565
  • filter parent dropdown on quick-edit for critical pages
  • Filter Customizer Static Front Page Dropdowns for critical pages
  • Make sure JSON-LD is valid JSON
  • Prevent Fatal error: Uncaught TypeError: Argument 1 passed to EEH_Schema::add_json_linked_data_for_event() must be an instance of EE_Event, string given

Enhancements

  • Modify EEH\_Activation::create_cron_tasks so it can allow setting the initial time for the first scheduled event to run
  • Add support for embeddable Calendar in an iframe
  • new template for ticket price details
  • hook into new action with new callback method and load new template
  • Extract iframe logic from Ticket Selector module and refactor as separate abstracted class so that it can be reused
  • Add robots meta tag to registration checkout, transactions, and thank you pages
  • Implement a filter for test sends to allow extra logic over the setting of messenger test field settings
  • Add front end user-interface for selecting a datetime before selecting tickets
  • Add method to EEM_Base for getting qualified column names for ALL fields on a table
  • send shipping data to PayPal Pro. Use registration info for this if possible, otherwise fallback to using billing info

January 17, 2017

Event Espresso 4.9.26.p
Bug fixes:

  • Don’t deactivate incompatible addons
  • Fix registration type messages not being sent when paying with PayPal Express on a SPCO re-visit
  • Always show each ticket type’s Quantity and Price info on reg checkout
  • Fix Fatal error: Call to a member function name() on boolean in core/db_classes/EE_Ticket.class.php on line 1090
  • Fix broken payment step on SPCO when using Braintree PM

New Features:

  • Add Schema.org JSON-LD for events
  • REST API – return a $schema property on options requests
  • Add filter hook to PayPal Express gateway to allow sending additional data to PayPal

January 12, 2017

MailChimp 2.3.4

  • Pass $registration and $EVT_ID to ‘FHEE__EE_MCI_Controller__mci_submit_to_mailchimp__subscribe_args’ filter

January 11, 2017

Braintree Payment Method add-on 1.0.5

Bug fixes:

January 10, 2017

Braintree Payment Method add-on 1.0.4

Bug fixes:

  • Update Braintree JS to use proper booleans
  • Remove default button parameter that is set to null

January 5, 2017

Event Espresso 4.9.25.p
Bug fixes and Enhancement:

  • Update EE_Datetime spaces_remaining to include reserved tickets too
  • Add checks for object instance before accessing methods
  • Add filter to allow target blank for Alternative Registration links

January 3, 2017

Event Espresso 4.9.24.p
Bug fixes:

  • Fix issue when jQuery validation disabled or WP_User active, SPCO form submission is failing
  • Fix the primary registrant info overwriting additional registrants if the last name question is not included within the personal info question group
  • Change State Dropdown select to use hide() && show() and the disable property for controlling valid options
  • Fix inconsistent capability restrictions on various registration admin page list table views
  • Add new EEM_Message status to represent when the messages system passes off a message to be processed by a messenger
  • Only delete failed transactions after a week if they have no payments
  • Add shims for get_preview_post_link() and is_post_type_viewable()
  • Plugin Update Engine: Don’t listen on POST requests for sitelicensekey saves when DOING_WP_CRON
  • Remove html tags from translation strings
  • Make PayPal Express order item names and descriptions filterable and consistent with other gateways
  • REST API: Filter/remove the self_wp_post link for events and venues when the WP REST API v2 plugin is active
  • Reword “Table existed when it shouldn’t exist” warnings
  • Fix ‘category’ typo within migration messages

Enhancements

  • Remove additional Attendee divs from display when no information is asked for additional attendees
  • Introduce new EventEspresso\core\services\assets\Registry class for loading scripts and queueing up data
  • Add button to the registrations list table to download the results of the current registration list table query into a CSV file
  • Add filter to model enum fields allowed_enum_values

You can review older changelogs from the changelog archives

Posted in | Comments Off on 2017 Changelog Archive

Wait List Manager

The Wait List Manager add-on allows you to automate the process of capturing wait list signups when your events sell out.

View quick links for this add-on –>

If the wait list is activated on an event, and the event sells out, a button will automatically display on the event details page that encourages attendees to join a wait list. If an attendee joins the wait list and someone cancels, the wait list attendee can be auto-promoted to the next available spot.


Need to Buy a Support License for the Wait List Add-on?
https://eventespresso.com/product/eea-wait-lists/

Wait List Installation

This add-on requires Event Espresso 4.9.49 or newer. It cannot be used with old versions of Event Espresso 4.

This add-on is a plugin for WordPress and can be installed through your WP dashboard (WP-admin).

Download the latest version of the Wait List add-on from your Event Espresso account.

Then login to your WordPress dashboard (WP-admin) and go to Plugins. Next, click on Add New –> Upload and browse to the plugin on your computer. Then select the zip file and begin the upload process. Wait for the plugin to upload and then click on Activate.

Setup and Configuration

Login to your WP dashboard and go to Event Espresso –> Events –> Choose an event.

You’ll now be viewing the overview screen for the selected event. Scroll about half way down the page, until you see the Event Wait List settings.

Event Wait List Settings

Event Wait List Settings

Usage

Once you’ve added a wait list to an event by adjusting the value of the “Wait List Spaces” setting and the event sells out, the ticket selector is replaced and a button will be displayed on the event details page. The “Sign Up For The Wait List” button allows potential attendees to sign-up to be on the wait list if spaces open up. Spaces can open up if someone cancels or is removed from the event list.

Wait List Front-end

This image shows a sold out event with the option to sign up for the wait list:

Sold Out Event w/ Wait List Sign Up

Sold Out Event w/ Wait List Sign Up

Wait List Sign Up Form

Wait List Sign Up Form

When a registrant uses the button to sign up for the wait list, then a popover is displayed to capture the attendee information:

Once all wait list spots are taken, the “Join The Wait List” button goes away:

Sold Out Event w/o Wait List Sign Up

Sold Out Event w/o Wait List Sign Up

Manually Processing Standby Registrations

Once registrants are added to the wait list, you can easily follow-up with them or promote their registration to approved, pending payment, and more, if any spaces open up for the event.

To manually promote registrants, head on over to the Registration List table filtered for the wait list:

Wait List Registration Overview

Wait List Registration Overview

Here you can get an overview of wait list registrations, promote registrations, view registrant information, and resend notifications.

To promote someone on the wait list to an open spot, simply click on the persons name or select the box and use the bulk actions to change the status. For this example, I will click into a single wait list registration to view the details:

Wait List Registration Manual Promote

Wait List Registration Manual Promote

From there you can change the registration status and send related messages. If you are running a paid event, you can use the “Pending Payment” option to make sure the attendees pay before taking a spot in the registration list. However, if you’ve promoted multiple attendees to “Pending Payment” and only have a limited number of spaces, then the first attendees to pay will receive their spot on the “Approved” registration list.

Warning!

Reducing available spaces after promoting registrants should be avoided at all costs.

Auto-promotion Settings

The Wait List Manager auto-promotion setting helps you by making sure wait list registrations are automatically promoted whenever a space opens up in the event. You can also leave some spaces on manual control if desired.

Wait List Manager Auto-promotion Settings

Wait List Manager Auto-promotion Settings

Wait List Messages

The Wait List Manager creates three additional messages that send when your customers sign-up for a wait list. To edit and manage the Wait List messages, login to your WP dashboard and go to Event Espresso –> Messages –> Default Message Templates.

Once on the Default Message Templates dashboard, you may need to navigate to the second page of messages. Once you are on the second page of the messages overview, you should see the newly added Wait List Messages:

Wait List Messages Overview

Wait List Messages Overview

From there you can edit the content of each message to meet your needs.

Available Options

  • None at this time — check back soon

Frequently Asked Questions

  • None at this time — check back soon

Troubleshooting

The plugin will not activate. Can you help?
Are you running a current version of Event Espresso 4? This add-on needs at least version 4.9.49.p to activate.

Where is the menu screen for this add-on?
This plugin does not create any new menus in the WordPress admin screen. It uses the messages setting screen along with the event editor for Event Espresso.

Customizations

Our support team cannot write custom coding for you. Below are some examples on customizing this add-on.
  • None at this time — check back soon
Need to Buy a Support License for the Wait List Add-on?
https://eventespresso.com/product/eea-wait-lists/

Posted in | Comments Off on Wait List Manager

How to set up a class that meets weekly

When you set up an event in Event Espresso you can create multiple datetimes, which works well for classes that meet weekly or bi-weekly.

  1. You go to add a new a event or edit an existing event
  2. Scroll to the Event Tickets & Datetimes box
  3. Input the first day and time the class meets. You can optionally give this datetime a name,
    such as “Week 1”
  4. Click the Add Datetime button
  5. Input the second date’s day and time, then click on Create Datetime
  6. Repeat

Notes:

  1. Setting limits for datetimes is optional if you set a Ticket Quantity and there’s only one ticket option. If there are multiple ticket options and there’s a class size limit, then it’s best to set a limit for the datetimes
  2. If you also sell “one-time” registrations for a single class, these can be set up as individual tickets that grant access to a single datetime. You click on the advanced options (gear icon ) to connect a specific ticket to a specific datetime

Posted in | Comments Off on How to set up a class that meets weekly

Chase Paymentech Orbital Gateway

The Chase Paymentech (Orbital) payment gateway will allow your attendees/registrants to pay for their event registrations with a credit or debit card on your website.

View quick links for this payment gateway –> 


Need to Buy a Support License for the Chase Paymentech (Orbital) Payment Gateway for Event Espresso 4?
https://eventespresso.com/product/eea-chase-paymentech-payment-gateway/

Installation

This add-on requires Event Espresso 4.9.26 or newer. It cannot be used with old versions of Event Espresso 4.

This payment gateway is a plugin for WordPress and can be installed through your WP dashboard (WP-admin).

Download the current version of the Chase Paymentech (Orbital) payment gateway for Event Espresso 4 from your Event Espresso account.

Then login to your WordPress dashboard (WP-admin) and go to Plugins. Next, click on Add New –> Upload and browse to the plugin on your computer. Then select the zip file and begin the upload process. Wait for the plugin to upload and then click on Activate.

Certification

In order to be certified to use this plugin and to receive production API credentials from Chase, you must complete the certification document Chase provides and submit it to Chase for review.

You can do that yourself or contact PluginIdeas.com who offers a Chase Paymentech Certification service.

Locate your Credentials for Chase Paymentech (Orbital)

Your credentials for Chase Paymentech (Orbital) will be provided to you by an account manager at Chase. You’ll let them know you’re using the Orbital gateway (not Authorize.net).

Chase Paymentech (Orbital) uses a Merchant ID, Username, Password, Terminal ID, and BIN for payment processing.

Will Chase Paymentech (Orbital) be the only payment method enabled or the only one you offer? Click here to learn how to make it selected by default during the registration checkout.

Setup and Configuration

An account with Chase Paymentech is needed to accept payments via Chase Paymentech.

A dedicated SSL certificate is recommended to make registration checkout and other areas of your website more secure.

Login to your WP-admin (WP Dashboard) and go to Event Espresso –> General Settings –> Payment Methods. Once on the Payment Methods screen, click on Chase Paymentech and click on the button to activate the payment method.

Below are the available fields and explanations for each field.

Name – This is the name of the payment method.
Description – This description is shown during registration checkout.
Admin-Only Name – This is a name of the payment method that will only be shown in the WP Dashboard (WP-admin).
Admin-Only Description – This description is used only in the WP Dashboard (WP-admin).
Debug Mode On? – Enables debugging for this payment method. It should be off (set to no) on a live/production site.
Open by Default? – This sets this payment method to be pre-selected on the registration checkout page.

To give your audience more payment options, you can activate multiple payment methods at the same time. However, if you are offering just one payment option, then we recommend that you set that one payment method to be selected by default during registration checkout. That will simplify the check out process for your attendees.

Merchant ID – This credential is needed to process payments and is provided to you when your merchant account is setup.
Username – This credential is needed to process payments and is provided to you when your merchant account is setup.
Password – This credential is needed to process payments and is provided to you when your merchant account is setup.
Terminal ID – This credential is needed to process payments and is provided to you when your merchant account is setup.
BIN – This credential is needed to process payments and is provided to you when your merchant account is setup.

Order – The value (number) can be used to sort or arrange this payment option. A lower value means that it should appear first during registration checkout.
Button URL – This is the URL to the image that will be used during the payment process of registration checkout.
Alternative Button URL: https://ee-screenshots.s3.amazonaws.com/2015/07/pay-by-credit-card.png
Pay by bank card
Usable From? – Select where this payment method should be available for use. This payment method cannot process payments through the WP-admin (WP Dashboard).
Update Settings – Click this button after making any changes to your payment method.
Deactivate Payment Method – Click this button to deactivate this payment method.

Usage

The Chase Paymentech (Orbital) payment gateway will let you accept payments through major credit or debit cards.

The XML API from Chase Paymentech (Orbital) is used which means that your registrants/attendees will pay for their registrations on your website.

An account with Chase Paymentech is needed to accept payments via Chase Paymentech.

Troubleshooting

I configured Chase Paymentech (Orbital) and payments are not being processed. Can you help?
Double-check that you are using your API credentials for production (live) mode. Also, ensure that there is no extra spacing before or after the credentials in the payment methods screen of Event Espresso 4.

How can I setup a recurring payment or subscription through Chase Paymentech (Orbital)?
Recurring or subscription payments are not currently supported in the Chase Paymentech (Orbital) payment gateway.

When I refund a payment, does it also refund through Chase Paymentech (Orbital)?
Refunds in Event Espresso 4 are currently a two step process. First, apply the refund through the transactional details screen of Event Espresso in your WP-admin (WP dashboard). Then login to your Chase Paymentech merchant account and process the refund.

Is an SSL certificate needed for Chase Paymentech (Orbital)?
A dedicated SSL certificate is recommended if you are accepting payments on your website.

Do I need to be PCI compliant?
Compliance with the Payment Card Industry Data Security Standards (PCI DSS) is required if you are processing, storing, or transmitting credit card data. Event Espresso recommends using a dedicated SSL certificate on your website.

View more information on PCI compliance from Chase Paymentech (Orbital).

Customizations

Our support team cannot write custom coding for you. Below are some examples on customizing this payment gateway.
  • None at this time — check back soon!



Need to Buy a Support License for the Chase Paymentech Payment Gateway for Event Espresso 4?
https://eventespresso.com/product/eea-chase-paymentech-payment-gateway/

Posted in | Comments Off on Chase Paymentech Orbital Gateway

EE4 Automated Upcoming Event Notification add-on

Currently in Beta Testing: The add-on is available for beta testing from the pre-release channel (PRC) within your Event Espresso account page. Once you’ve signed up for the PRC, the download will be available in the EE4 tab of the PRC. Github.com users can download the add-on from our Github page (under the name “eea-automated-upcoming-event-notifications”). Please note that you might have to manually update the plugin when we roll out the full version of the add-on.

The Automated Upcoming Event Notification add-on will allow you to send a reminder email to your attendees about an upcoming event automatically. This can be used as a courtesy reminder to your guests about upcoming events and you can also customize this on a per-event basis. For example, you can automatically notify attendees/registrants three days before the start of one of your events.

View quick links for this add-on –> 

Installation

This add-on requires Event Espresso 4.9.39.p or newer. It cannot be used with old versions of Event Espresso 4.

This add-on is a plugin for WordPress and can be installed through your WP dashboard (WP-admin).

Download the current version of the Automated Upcoming Event Notification add-on for Event Espresso 4 from your Event Espresso account.

Then login to your WordPress dashboard (WP-admin) and go to Plugins. Next, click on Add New –> Upload and browse to the plugin on your computer. Then select the zip file and begin the upload process. Wait for the plugin to upload and then click on Activate.

Setup and Configuration

You will not see any new WordPress administration menus for the add-on. Upcoming Event Notifications (event reminders) are set up through the existing Messages System which can be found in WordPress admin > Event Espresso > Messages > Default Message Templates page. If you do not see them on the page, then try adjusting the pagination through Screen Options in the top right area of your screen. Increase the value to a higher number such as 25 and then click on the Apply button to save changes.

Messages - Upcoming Event Notification

Please note: if the new message templates (shown in the screenshot above) are missing, then please make sure the Email messengers are active in Event Espresso > Messages > Settings.

Usage

This add-on introduces two new message types:

Automated Upcoming Event Notification

In this message type, the automation is triggered by the threshold against the earliest date-time on the event. This is ideal if you have an event with multiple (or single) datetimes but want to send out the notifications for just the event.

Automated Upcoming Datetime Notification

In this message type, the automation is triggered by the threshold against specific date-times as opposed to individual events, which is ideal for when you are using an Event to represent multiple occurrences of that same event via datetimes.

Activating automated upcoming notifications for ALL events or datetimes

First, you need to decide if you want to send a single automated event reminder or a reminder for each datetime across ALL events. If not, then please move on to the next section. However, if you would like to have the reminders to sent automatically, on a default schedule, then simply follow these steps:

  1. Visit the WordPress admin > Event Espresso > Messages > Default Message Templates page.
  2. Choose the message automated upcoming message type you want to work with (Upcoming Event or Upcoming Datetime) and click edit.
  3. Scroll down the page a little to find the Scheduling Settings meta box in the right area of the page, where you can turn the scheduling on and set the number of days before the event or datetime to send the automated notification.

Once you have activated the scheduling, Event Espresso will email the registrants X days before the event.

Activating automated upcoming notifications for a single event

To activate the automated event reminders for a single event, visit the event editor for that event, then scroll towards the bottom of the page where you will find the Notifications panel. From there you can decide which upcoming notification (event or datetime) to send for that event, then click the Create New Custom button to create a custom automated notification for your event.

Event Editor - Upcoming Event Notification

Next, once you’ve created a custom template, click the Edit button. Then scroll down the page a little to find the Scheduling Settings meta box, where you can turn the scheduling on and set the number of days before the event (or datetime) to send the automated notification.

Once you have activated the scheduling, Event Espresso will email the registrants X days before the event.

You can then save changes to your event by clicking on the Update button in the event editor.

Default behavior across both message types:

  • The “default” templates for these message types apply globally to all events but have a toggle for turning the messages off or on globally, which ensures that if you have a more simple setup, where you just want the same template to be used across all of your events/datetimes. You can just toggle the default template on or off.
    Please note: the setting defaults to off because having both on means registrants would receive multiple “upcoming” notifications for the first datetime on an event.
  • By default, the message types will be sent to the contact details for registrants (only one email per contact, regardless of registrations sharing that contact) and would only get sent to APPROVED registrants.
  • Event specific templates can be created that will override the default and would also have an on/off toggle for the message type.
  • The ONLY option (besides the on/off toggle) for these message types is how many days before the event/datetime (depending on message type) the messages get generated and sent.
  • This will only send to approved registrations for Events that are “upcoming” or “sold out” active status. The actual query will be based on whether there’s a date in the future for an event (matching whatever optional – the only option – threshold people pick.). For the upcoming event message type (not the upcoming datetime), there will only be ONE message go out and it will get triggered against the earliest datetime for that event.
  • The shortcodes available for the templates will be the same as the registration message types because the recipients are registrations.

Troubleshooting

The plugin will not activate. Can you help?
Are you running a current version of Event Espresso 4? This add-on needs at least version 4.9.39.p to activate.

Where is the menu screen for this add-on?
This plugin does not create any new menus in the WordPress admin screen. It uses the messages setting screen along with the event editor for Event Espresso.

Recommendations

  • If you have ever experienced email deliverability issues with your server, or are on shared/inexpensive hosting, or emails are getting lost or marked as SPAM or junk mail? Then a transactional email service is HIGHLY recommended when using this add-on for Event Espresso 4.
  • This add-on uses Cron tasks to run scheduled callbacks or spawn cron for all scheduled events. This means that you will need a server that is capable of running Cron jobs (a unix program which runs unattended scheduled tasks).

Customizations

Our support team cannot write custom coding for you. Below are some examples on customizing this add-on.
  • None at this time — check back soon

Posted in | Comments Off on EE4 Automated Upcoming Event Notification add-on

Using Contact Form 7 to create wait lists for your events

First install Contact Form 7 through the plugins manager within your site, navigate to Dashboard -> Plugins -> Add New and search for ‘Contact Form 7’. This first result should be Contact Forms 7 and looks like this:

Click ‘Install Now’ and activate, you’ll now have a ‘Contact’ section in your admin menu which you can use to generate contact forms.

Within the Contact section click ‘Add New’ to generate a new form:

Create a new form and add the details you want to see on that form, at a minimum we recommend name and email, although you can request any details you need and also include any additional text on the form, for example ‘Join the waiting list for this event?’ For example:

When any users submit the form you’ll receive an email with the details they submitted, however currently we don’t have any details of the event within the form, or the email so we won’t know which event they wish to sign up for but we can add those details within the ‘Mail’ tab.

The sections you will need to edit are ‘Subject’ (your form likely does not have a ‘subject’ field so manually set this) and then within the message body you’ll need to include details of the event. You can do this using the Contact Form shortcodes [_post_title] which shows the title of the post the form was submitted from and [_post_id] which shows the ID of the post the form was submitted from. Here is an example:

You may also want to update the text within the ‘Messages’ tab to suit, the text there is shown to users through various steps of the form.

Now you have a waitlist form within Contact Form 7 we need to use a small function to output that form on sold out events. First take note of the shortcode shown at the top of your contact form (the blue box in the screenshots above), you will need this to pull the correct form, in my example this is `[contact-form-7 id=”107″ title=”EE Waitlist”]` so we can use this function:

You can add that function to your themes functions.php file or create a Custom Functions Plugin and place it within that, be sue to use the correct shortcode to pull your form in.

Now on your sold out events you should see something like this:

Whenever a user submits the form you will receive and email from contact form 7 with the users details along with the event title and ID.

Posted in | Comments Off on Using Contact Form 7 to create wait lists for your events

Do NOT follow this link or you will be banned from the site!