|
Thomas Richards
|
July 12, 2012 at 9:19 am
When I try to change an event (like up the attendee limit or change the registrations times) I press “Update Event”, and get the notification box that the event has been updated, but the changes revert back to the prior state.
This happened when I upgraded to 3.1.24.1. I then auto-upgraded to 3.1.24.2, and the problem persists. I then deleted and reinstalled the plugin (3.1.24.2) and the problem persists.
The permissions on the plugin files are all the same as my other plugins (and fairly permissive) and I’ve confirmed I have no issues with CRUD commands in those plugins.
This is on a multisite installation, but the event espresso plugin is not network activated.
Any ideas?
|
|
Josh
|
July 12, 2012 at 11:26 am
So was this working before you updated to 3.1.24.1? If so, which version did you have prior to updating? Are there any customized functions built off the previous version?
|
|
Thomas Richards
|
July 12, 2012 at 11:51 am
Yes, it was working on the prior version. I don’t remember the prior version number but it was really close to the latest, I think 3.23.?.
I have nothing customized. I have moved some template files (the checkout pages) and customized them, but nothing in the core of the plugin.
|
|
Josh
|
July 12, 2012 at 12:58 pm
Has anything else on the site changed since updating from 3.1.23.P? We haven’t seen any other reports like this one. One thing you could check is for older versions of the add-ons.
|
|
Thomas Richards
|
July 12, 2012 at 3:15 pm
I’ll look at older versions, but as a troubleshooting step I deactivated all plugins (including the Event Espresso add-ons). I made sure there weren’t any MySQL database permission hang-ups (though none of this has changed) and of course WP directory permissions look fine.
I don’t even know what to do next to troubleshoot.
|
|
Josh
|
July 12, 2012 at 4:03 pm
If you need a copy of Event Espresso 3.1.23 to test let us know.
|
|
Seth Shoultes
|
July 13, 2012 at 7:27 am
It could be that the ticket_id field was not added to the wp_event_details table in the database.
The new ticket_id database field was added to facilitate the ticketing addon. On activation of the new version of Event Espresso, WordPress tries to add the new field automatically. This works pretty well on most servers, however it sometimes fails for various reasons. Most of the time the failures are the result of server configuration, outdated MySQL database software, or the server is running IIS (Windows) based technology.
Sometimes the following steps help to resolve the problem. If not, you will need to go into the database and add the new field manually to the “wp_events_detail” table.
Steps to try and resolve automatically:
- Deactivate the new version
- Activate an older version
- Deactivate the older version
- Activate the new version
- Test to see if that fixes it
|
|
Thomas Richards
|
July 13, 2012 at 10:30 am
We aren’t running IIS or outdated MySQL software.
I reinstalled every plugin, and for whatever reason that fixed it.
|
