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
Upgrading without losing all formatting | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Upgrading without losing all formatting

Upgrading without losing all formatting

Posted: December 13, 2012 at 4:14 pm

Viewing 5 reply threads


Ingrid Schroder

December 13, 2012 at 4:14 pm

Hi guys,

I’ve upgraded to wordpress 3.5 and experiencing issues as I haven’t upgrated to latest Event Espresso.

This is what’s appearing when I upgrade and event:
http://i48.tinypic.com/ajqtkj.png

This is what appears on registration, also price is showing as $0.00: http://i47.tinypic.com/2zqu6h2.png

This is what appears on registration confirmation: http://i45.tinypic.com/jhsnk5.png

We were due to launch the new site today for the client, but we’ve done so much work formatting everything in Event Espresso that I’m petrified that when I upgrade that we’ll lose everything – as happened when we upgraded last time.

How can we get around this?

Appreciate your help.
Ingrid


Jonathan Wilson

  • Support Staff

    •

December 14, 2012 at 3:24 pm

Hi Ingrid,

Yes, those errors are fixed in the latest update.

Following the instructions on the page to update: http://staging.eventespresso.com/wiki/updating-event-espresso/

Make sure you do a backup of your files and db. (This is a best practice for any updates for any software.)

Pay particular attention to the 11th bullet point (when you get to it). It will explain how to keep your changes in the updated templates.

Let us know if you have any issues along the way.


Ingrid Schroder

December 18, 2012 at 3:41 pm

Ok thanks, the formatting looks good.

But still having issues with registration showing as $0.00 ??


Josh

December 18, 2012 at 4:08 pm

Hi Ingrid,

Can you check the /wp-content/uploads/espresso/templates directory for templates from a prior version? If there are any templates in that folder, these will need to be removed or updated to be compatible with the current version.


Ingrid Schroder

December 18, 2012 at 4:11 pm

All of my templates were merged using Diffmerge so they are current…. is it perhaps the gateway files?


Josh

December 18, 2012 at 4:38 pm

If you have old gateway files in /wp-content/uploads/espresso/gateways, this can cause problems after updating. Also, have you checked and verified that all the add-ons were updated to the latest versions too?
Viewing 5 reply threads

The support post ‘Upgrading without losing all formatting’ 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, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server