Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Detailed Changelog | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Detailed Changelog

Detailed Changelog

Posted: October 15, 2012 at 9:53 am

Viewing 1 reply thread


Melissa

October 15, 2012 at 9:53 am

Is there any way to get a detailed log of which actual files have been modified on updates? I have version 3.1.26.P installed currently and have done heavy customization to get EE to work how I need it. I am experiencing the issue described in the fix for 3.1.27.1.P (question groups not appearing/saving) and don’t want to overwrite all my custom edits. What’s the best way to upgrade?


Josh

October 15, 2012 at 10:14 am

Hi Melissa,

We do not have a list of files that were changed from version to version. Whenever there is a change to one of the template files that needs to be updated, we’ll make a note in the change log. As an example, the shopping_cart.php template was changed in 3.1.26, so if someone had made changes to it, this file needed to be updated when they updated to 3.1.26.

What I can suggest is using a tool like diffmerge to compare the files that you’ve changed to the new version. This will pinpoint exactly where in each file the changes were made, and whether your changes are affected.

Typically most changes are made in the templates files, in which case you can simply copy these over to /wp-content/uploads/espresso/templates

Please see this guide for more information on where to copy modified templates:
http://staging.eventespresso.com/wiki/put-custom-templates/
Note that some templates need to be copied over in pairs. For example, if you make a change to event_list_display.php, you’ll need to copy over its counterpart event_list.php. Also please note that if we need to make a change to a template in version of Event Espresso, you’ll need to copy this change into your custom template to stay current with the plugin.

If the changes are outside of the templates, many of Event Espresso’s functions are pluggable and can be overwritten by using the custom files add-on.

Viewing 1 reply thread

The support post ‘Detailed Changelog’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server