|
Mike Wilson
|
October 16, 2014 at 9:01 am
Hi,
WordPress 4.0
Event Espresso Version 4.4.3.p
Event Espresso – Calendar Version 3.1.0.p
Existing Installation updated on Friday, Oct 10
Browsers – Chrome Version 38.0.2125.104, FireFox Version 32.0.3
We are not currently using EE’s built in registration process, but the events area of our site can be reached here: – https://www.premierinc.com/events/
Usecase – Any user (including admin) unable to edit an existing (active or expired) event’s status or visibility – e.g. set status to “draft”. Under Update Event > Status > Edit clicking edit does nothing but append “#post_status” to the url string. Page does not refresh. No edit options are presented. Nada.
Steps taken – Disabled all plugins individually and retested without success.
Our theme is custom, in-house based on Roots. I have had zero issues with the backend up to this point and have not recently committed any code to prod other than updating the EE plugin. We cannot easily switch to TwentyFourteen for testing, but given this issue is on the back-end, that doesn’t seem to be relative.
|
|
Tony
|
October 16, 2014 at 9:18 am
Hi Mike,
Can I ask who your host is please?
Within the event editor, can you open either Chrome dev tools (Settings -> More Tools -> Developer Tools) or Firebug and open up console. Refresh the event editor, do you see any error being thrown?
|
|
Mike Wilson
|
October 16, 2014 at 11:28 am
Hi,
We host with WPEngine – Enterprise. I do not see any errors in the console.
|
|
Mike Wilson
|
October 16, 2014 at 11:31 am
I also noticed this issue is presenting for the “Published on” setting as well.
|
|
Lorenzo Orlando Caum
|
October 16, 2014 at 1:46 pm
Hi Mike,
WP Engine deactivates a feature called heartbeat in the WordPress admin. Please open a support ticket with them to have it restored.
We also have this workaround available which restores it:
https://gist.github.com/b4aa84c0938afdec2c5d
It can be added to your child theme’s functions.php file or a site specific plugin:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
Thanks!
—
Lorenzo
|
|
Mike Wilson
|
October 16, 2014 at 2:15 pm
Hi,
Thanks for the workaround, that seemed to solve the issue.
That being said it concerns me that heartbeat is an issue for EE. I don’t know the WEP policy and we have folks working in the admin all day, obviously with open sessions, so the concern is this will cause me some trouble down the road due to high CPU usage.
Why is it that you require heartbeat so that these normal admin post functions (functions that work without it in pretty much everything else I’ve tested) work properly?
|
|
Mike Wilson
|
October 16, 2014 at 2:30 pm
Also we didn’t see this issue until the latest update so is this something new that was introduced to the plugin?
|
|
Lorenzo Orlando Caum
|
October 16, 2014 at 7:59 pm
Hi,
We use the heartbeat feature from WP for a couple areas in Event Espresso. The primary area is to handle delayed PayPal IPN updates.
This is what marks the registration as paid.
—
Lorenzo
|
|
Mike Wilson
|
October 17, 2014 at 10:23 am
Hi,
Thanks for the response Lorenzo. That was a pretty vague answer in the context of this issue, but I understand. As long as WPEngine doesn’t have an issue with your workaround, I’ll consider this one resolved.
And FYI I also found this plugin on Github, so you might want to take a look at it and see if it works or is more convenient for your WPE customers.
|
|
Mike Wilson
|
October 17, 2014 at 10:24 am
WPE-Allow-Heartbeat
|
