|
ningram
|
January 15, 2013 at 8:20 pm
I just had to spend the evening tonight combing through all the template files I had customized for a client’s web site to make the checkout process less clunky to suit their wishes. Although I had planned to spend a nice evening with my kids, I was instead forced to update a client web site because the recent EE update broke all the customizations I had made to the template files which were moved to the uploads folder per your instructions.
I lost several hours of my life because you guys have a system where customizations, while moved OUTSIDE the plugin folder by your design, might still need to be overwritten. That is ridiculous.
I’ve never dealt with a premium plugin that provided an option for customization, but then required those customizations to be re-customized on an update. The whole purpose of moving the template files to the uploads folder is so they don’t get overwritten by an update!
For as much as you charge for the Event Espresso plugin and support, this scenario never should have happened.
I certainly hope you will address this issue. I cannot in good conscience recommend Event Espresso again until you do.
Regards,
Nathan Ingram
|
|
Dean
|
January 16, 2013 at 1:05 am
Hi Nathan,
I am really sorry about your lost time and effort here, and I understand fully how the current template system can cause frustration.
It was designed so that the templates wouldn’t be over written on updates, which is still the case, and would normally only be modified irregularly meaning clients would only need to modify them irregularly as well.
Due to us adding lots of new features and changing certain elements in order to improve the plugin and the templates, they are being changed more often of late, which is causing customers such as yourself to have to update them more often.
We are fully aware that this system isn’t ideal and we are working towards a better system, one where logic and structure are separated so that updating templates becomes a minimal task or even a none existent issue.
This is likely to be implemented in the 3.2 version which is being worked on currently, as the plugin is making a shift in architecture that will allow us more freedom in how we deal with the templates.
I really hope that you can bear with us as we continue to improve Event Espresso to make it an easier user experience and more feature filled.
|
