TorontoCPR had Event Espresso 188.8.131.52.P installed in 2015 with various customizations, which prevented the plug-in from being updated. In 4th-quarter 2017, we decided to migrate to Event Espresso 4 and outsourced developers to apply the prior customizations from version 3 to 4. With successful completion of the customizations, there are several tasks that need to be done before final deployment from the staging server to the live server.
Migration to localhost:
In order to work on the following tasks, the version of the site on the rexzetsolutions staging server needs to be migrated to your localhost. This has the most recent version of the code, but also was using the live data from 4th quarter 2017. Any new entries into the live database will not be on the rexzetsolutions database and will need to be imported and converted. The EE4 forum has several topics on this:
[login to view URL]
The first time we converted the database into EE4 format took overnight, but it was the EE4 migration tool that took a long time as it had to process the database since 2015. It may not take that long since this now just involves adding data from around October 2017.
E-mails to Messages:
Event Espresso 3 used an “Email Manager” to create and edit e-mail templates with shortcodes that would be sent when users register for a course on successful payment while Event Espresso 4 uses a “Messaging” system. TorontoCPR has exactly 20 e-mail templates in total that would need to be reconfigured for Event Espresso 4. Examples of a typical EE3 e-mail template and screenshots of EE3 vs EE4 message system are provided. ([login to view URL], [login to view URL], etc.)
2 possible bugs:
After the outsourced developers completed their tasks, we tested it out on the staging server and found 2 bugs:
a) Using the search feature in the regular WordPress sections (outside of Event Espresso) resulted in an error page saying “Service Unavailable”
b) Changing a registrant’s event details (for example, if they wanted to reschedule) would produce the same “Service Unavailable” page.
Reconfiguring Pages to update shortcodes with new venue IDs:
The main issue that TorontoCPR faced when upgrading from EE3 to EE4 was that it broke the customization of allowing multiple venues to be displayed in an Event listing on the front-end. While this was fixed by the previous developers, all of the pages that display events need to be updated with new event_category_id numbers in their shortcodes as EE4 now references that value with 4 digit numbers now.
Example of EE3 event shortcode:
[ESPRESSO_VENUE_EVENTS_MULTIVENUE id="21" event_category_id=33 show_recurrence=true css_class=single-event-list-class]
Example of EE4 event shortcode:
[ESPRESSO_VENUE_EVENTS_MULTIVENUE id="21" event_category_id=1350 show_recurrence=true css_class=single-event-list-class]
For this, there are 14 pages where the shortcodes need to be updated:
• 7 pages, which can be visited from the “Sign up for a course” link on the top menu. These pages are categorized by course and within each course, display events by geographic location, and each geographic location can have multiple venues;
• 1 page for the George Brown course, which just displays 1 event by 1 venue;
• 6 pages, which can be visited from the home page navigation near the middle of the page right below the slider image. These pages are categorized by geographic location and within each page, display events by course type, and each course type can list multiple venues.
After successful completion of the above and making sure EE4 works the same as EE3, you can deploy the site to the live server. Of course, you will need to create a backup of the current site and database beforehand, but after, the new site should be deployed (I recommend scheduling a date and time with Andre for deployment so it does not interfere with regular business hours).