|
Eric C
|
November 3, 2015 at 1:54 am
I am building a website that uses Event Espresso 4. I had to modify some of Event Espresso’s core functionality. For example, I modified some of the code in ‘EED_Espresso_Calendar.module.php’, ‘EEH_Event_View.helper.php’ and ‘EED_Ticket_Selector.module.php’.
Now I am afraid that down the road, if the client ever updates Event Espresso, my changes will be lost.
Was there a better way to do this? Is there a way I can override default Event Espresso functionality so that if an EE4 update is applied, I don’t lose all of my changes?
|
|
Lorenzo Orlando Caum
|
November 3, 2015 at 7:22 am
Hi Erin,
Changes to the events calendar will be lost when you update as it does not support templates.
However, there are templates available for various Event Espresso pages such as the events listing page, single event pages, venue pages, along with the ticket selector itself.
Could you provide an overview of the changes that you made so we can share feedback on how to move those changes to custom templates?
Thanks
—
Lorenzo
|
|
Josh
|
November 3, 2015 at 7:26 am
Hi Eric,
A good practice is use filter and action hooks via the WordPress plugin API. If there’s a spot in the plugin where you could benefit from a new hook, you can open a pull request to add the hook.
https://github.com/eventespresso/event-espresso-core/issues
|
