Conflict with Event Espresso

  • When I tried to install Elastic Email Sender on a site I have Event Espresso on, the backend of the site crashes. I went through one by one and deactivated plugins from the background, and it became quickly apparent that Event Espresso and your plugin could not be activated at the same time. I NEED both of these plugins on this website. I have also sent an email to Event Espresso, as one of you needs to update your code.

Viewing 1 replies (of 1 total)
  • Thread Starter promofuse

    (@promofuse)

    Here is the response from Event Espresso. In short, it appears you both are using the same constant. I’m hoping there’s a way you can change yours, as Event Espresso is a MUCH larger plugin and can’t update their code.

    So the issue is that both Event Espresso and Elastic Email are defining a constant names EE_ADMIN, if Elastic Search defines it earlier than Event Espresso, EE will throw a fatal as it then can’t files based on the location normally set in the constant.

    All EE constants are prefixed EE_, see here:

    https://github.com/eventespresso/event-espresso-core/blob/master/core/espresso_definitions.php#L35

    The Elastic Email plugin is using EE_ADMIN as a ‘flag’ to say if Elastic Email has loaded within the admin.

    5 matches across 5 files: https://monosnap.com/file/kSWdCj6PKZj6lOqoUSgiJy8OrB4EOa

    So to be honest, it makes the most sense for the Elastic Search Plugin to update that constant to something like EES_ADMIN which will require minimal change and the least amount of testing.

Viewing 1 replies (of 1 total)
  • The topic ‘Conflict with Event Espresso’ is closed to new replies.