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
Security fixes in templates | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Security fixes in templates

Security fixes in templates

Posted: May 16, 2013 at 4:32 pm

Viewing 2 reply threads


ablears

May 16, 2013 at 4:32 pm

Hello. I have highly customised EE template files. I’ve upgraded to 3.1.32.2.P from  3.1.21.P and am getting the ‘Sorry, there was a security error and your registration was not saved’ message when registering for an event. Rather than port all my changes across to the latest template files supplied with 3.1.32.2.P I’d like to just port the security fixes into them. Do you have a changelog for those fixes so I can see what to change?

 

thanks

Anthony


Josh

May 16, 2013 at 5:08 pm

Hi there,

There isn’t a detailed change log from version .21P. for the specific changes. Besides the nonce checks (for security) there are also changes to the price functions and the event list queries that will need to be updated too.

What you can do is use a tool called DiffMerge (it’s free to download) to merge your changes from the .21 templates into the new templates.


ablears

May 16, 2013 at 5:39 pm

Thanks Josh, I’ll go down the code merge route.

 

cheers

Anthony
Viewing 2 reply threads

The support post ‘Security fixes in templates’ 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.

The original Forum description...

Status: closed

Updated by ablears 11 years, 9 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server