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
Upgrade issues | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Upgrade issues

Upgrade issues

Posted: December 18, 2012 at 8:45 pm

Viewing 3 reply threads


scrair

December 18, 2012 at 8:45 pm

I went forward with the latest updates, first installing WordPress 3.5, then upgrading EE to 3.1.29.1P (from 3.1.20P). I am running into issues with registrations.

After filling in attendee info and clicking ‘Submit’ I either get a blank page or a page showing a $0 balance and no attendee name.

In my previous version I had customized some of the templates to change the wording, etc. I didnt think this would effect the upgrade, not sure if it does really.

I have gone ahead and updated the calendar plug-in and all relevant add-ons.

But, I have De-activated the new version in favor of my previous version so that the site stays functional. Please let me know what to do from here to get the newest version going. Thanks.
Stu Crair
http://www.fcdigitalworkshop.com


Dean

  • Support Staff

    •

December 19, 2012 at 1:22 am

Hi

Yes your customisations will affect the new version. The template files change from time to time (especially true if you are skipping several revisions like you have done) and because of that the old templates will break the site.

You need to rename the uploads/espresso folder and then look at porting your modifications to the new versions of the templates.


scrair

December 19, 2012 at 9:40 am

I appreciate the reply. Is there documentation on the best way to handle this migration? With custom templates involved?

I thought that since this was a newer version of the plugin, it would create the ‘new’ uploads folder, and then I could copy my code into the files as needed. But, it doesn’t sound like that is the case.

I have reset the site from a backup so WP and EE are back to previous versions and I can go forward with a little better direction. Thanks.


Josh

December 19, 2012 at 6:04 pm

Hi there,

In a nutshell, if there are customizations in /wp-content/uploads/espresso/templates or /wp-content/uploads/espresso/gateways, then the specific customizations will need to be copied line-by-line and if need be adapted to work with the new templates that ship with the new version. We recommend using Diffmerge to help merge changes into custom templates. This is more of a developer feature and should only be used by those who are comfortable with modifying PHP code and can take responsibility for maintaining the customizations.

Please see this article in the blog for more info:
http://staging.eventespresso.com/2012/12/what-you-need-to-know-about-upgrading-wordpress-and-event-espresso/#update-templates
and
http://staging.eventespresso.com/wiki/put-custom-templates/
Viewing 3 reply threads

The support post ‘Upgrade issues’ 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 Josh 12 years, 2 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server