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
Updating to 3.1.26.P | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Updating to 3.1.26.P

Updating to 3.1.26.P

Posted: September 12, 2012 at 9:34 am

Viewing 3 reply threads


agianni

September 12, 2012 at 9:34 am

Hi – I have a problem whenever I try to update. I deactivate the old version – then activate the new one – and my pages are screwy. I revert to the old version and I’m fine again. I think it has to do with some customization we have done – and I’m sure that there is one file that I just need to bring from the old version to the new version – but I have no clue what file that might be. Hoping I might get some hints on this…


Dean

  • Support Staff

    •

September 12, 2012 at 11:42 pm

Hello Agianni,

Without knowing more information it’s difficult to assist. What version are you upgrading from?

Have you checked the files dates to see if any are more recent and thus changed? That might give a clue as to where the customisations are.


agianni

September 21, 2012 at 6:51 am

Hi Dean,
Thank you. I’m trying to go from 3.1.20.P to 3.1.27.P. When I deactivate .20 and then activate .27 – I get these warnings where the events are supposed to show up.

Warning: preg_match() expects parameter 2 to be string, array given in/home/fusionp/public_html/fusionteachertraining.com/wp-includes/wp-db.php on line 1107

Warning: preg_match() expects parameter 2 to be string, array given in/home/fusionp/public_html/fusionteachertraining.com/wp-includes/wp-db.php on line 1109
There are no events currently scheduled

My team has told me that they put all of the customization stuff into the custom files folder per EE – so that the upgrades won’t effect anything. So I guess that’s not the issue.

Hoping for some suggestions. thanks!
angelo


Dean

  • Support Staff

    •

September 21, 2012 at 8:23 am

Hi,

Though generally the templates dont change as quickly as the core files, they do get updated periodically and reading through the Change Log shows that there has been some changes between your version and the current latest version.

I would test the latest version with the default templates and then with yours, if the error isn’t there with the default templates and appears when you introduce yours, then your custom templates will need updating.

A program such as DiffMerge can assist with reviewing the changes between the files.
Viewing 3 reply threads

The support post ‘Updating to 3.1.26.P’ 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 Dean 12 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server