We know you are all anxious to get your hands on Event Espresso 3.2. We know you have been patiently waiting for a date, and every date we have given has come and gone. We want you to know that we’re just as anxious to release Event Espresso 3.2 as you are to use it. While I can’t give you a date for when that will be, I will give you our current plan for a beta release:
We are in the process of adding the payment gateways back in. The registration system is mostly done with this being the last major piece.
We will be adding a script to the plugin that will check if there are existing Event Espresso databases present on the install. If there are, it will halt the installation of 3.2 until we have written an upgrade script. This will prevent you from damaging your existing Event Espresso installation as you preview the features of 3.2. This will enable you to safely start building/adapting new registration page templates and converting any customized templates you may have had over to the new system.
Once we have these two things, we will release a beta of 3.2 into the forums. There will be parts of the admin that will be missing, because they haven’t been completed yet, but they will be before we release a final version.
This has been a major undertaking. To give you an idea of just how much has changed (much of it rebuilt from scratch), I took a bunch of comparison screenshots of existing screens in 3.1 and their new counterparts in 3.2.
3.1 Event list
3.2 Event list
3.1 Event registration page
3.2 Event registration page
3.1 Multiple ticket type checkout
3.2 Multiple ticket type checkout
3.1 Multiple ticket type checkout — attendee information (copying a single attendee’s information to all attendees)
3.2 Multiple ticket type checkout — attendee information (copying a single attendee’s information to all attendees)
No plans to add BuddyPress integration in 3.2. If you’re having BP issues with the current version of the WP user integration, simply comment out or remove the following code from espresso-members.php in the espresso-members plugin directory:
/* Only load code that needs BuddyPress to run once BP is loaded and initialized. */
function espresso_bp_init() {
require_once("bp_event_class.php");
require_once("bp_event_template_class.php");
require_once("bp_functions.php");
}
add_action( 'bp_include', 'espresso_bp_init' );
Looks great, however, there is one big question I have about 3.2 MER and I see the “Copy From” which would indicate that every attendee still has to be named within the database, I asked previously about this use case:
2 adults at price point 1 and 2 kids at price point 2 attending. I want to buy the 4 tickets and only register 1 name, the name of the adult who will be paying – I don’t want to have to record any information due to the fact that there is a child at a different price point attending, which is currently the case – This is very confusing for users who are trying to book tickets in this manner and is leading to a lot of cart abandonment on my site.
Can you give an update on this please as I need to make some plans for a Christmas event and this will be a clincher as to whether we can continue to use Event Espresso or not.
It’s kinda hard to show the animation in a screenshot, and the current implementation is subject to change, but here’s a view of the mult-attendee reg form (arrow added for clarity)
After checking the box, the entire form collapses with an animation, leaving a link to show the reg form again and a button to move on to the next step:
Curious to know if there is any new handling of recurring events? Looks great by the way excited for the stable release.
Viewing 10 reply threads
The support post ‘Event Espresso 3.2 Comparison Screenshots’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.