|
BCPTA
|
August 1, 2017 at 4:39 pm
Hi there, I’m curious if the Heartbeat API is needed on all pages of a site, including all admin pages for EE4 to work?
I saw this and thought I should ask:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
I’ve installed a plugin that would allow the following options and curious if I can use any of them without affecting EE4?
https://cloudup.com/c5oD1AohudQ
Options are:
- WordPress default
- Disable everywhere
- Disable on dashboard page
- Allow only on post edit pages
Can I use any of these options?
This is the plugin link: https://wordpress.org/plugins/wp-disable/
|
|
Tony
|
August 2, 2017 at 2:04 am
Hi Johanna,
EE4 needs the Hearbeat API on the thank you and create new/edit event pages.
On the thank you page it is used to check for payments and payment updates in the background.
On the create new/edit page it’s used for a few functions.
You should be able to use ‘Disable on dashboard page’ without causing problems with EE, but there no really advantage to doing that imo.
Can I ask why you want to disable Heartbeat?
|
|
BCPTA
|
August 4, 2017 at 12:23 am
I’d like to speed things up and reduce the resources it takes up. It looks like that may be hard to do with this plugin operating though, unless it’s done on specific pages?
|
|
Tony
|
August 4, 2017 at 3:26 am
Heartbeat isn’t going to help all that much.
Event Espresso already jumps through multiple hoops to try and ensure that it only loads what it needs when it needs them, it should not be loading multiple resources on all pages unless you have EE specific shortcodes/functions that require them.
Can you be more specific on which load you are trying to reduce and what are you trying to speed up? Page load?
|
