I was hoping I could (privately, if need be?) find out exactly what changed in 3.1.37.2 so that I could replicate that change in our copy of the plugin to prevent the 60 character Event title limit for our client.
Unfortunately the plugin was heavily customized by a previous developer, so there’s not much we can do in the way of updating. I was hoping you’d be nice enough to let me know the details on how exactly the database insert problem was fixed.
Hi David, there were a handful of changes across several files. We can share those with you (links to text files with the diff) and you can review and manually apply them. However, it would be best to update to the current version of Event Espresso 3.
Could you follow up with us via the email below and also include a link to this support post and let us know your current version number?
Here’s a list of the files that were touched in the commit, it would be best if you can run a diff on these files in the current version and compare them to your copy.
and the version numbers near the top of espresso.php will need to be incremented to trigger the database update (eg, if you’re on 3.1.36.6, you change the version numbers to 3.1.36.7, deactivate EE3, then reactivate).
It worked perfectly. Surprisingly it wasn’t the event_name field that was the only one causing issues. I tested just changing that one in the DB setup, and it still went awry. Changing all the fields to the new lengths worked great.
Yes, we changed more than just the event name field, the price name fields could also go over and WP will prevent saving if characters get input past the character limit.
Viewing 4 reply threads
The support post ‘Changes in EE 3.1.37.2’ 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.