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
EE Update 3.1.28.3 errors | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › EE Update 3.1.28.3 errors

EE Update 3.1.28.3 errors

Posted: November 13, 2012 at 8:14 am

Viewing 3 reply threads


Chris Smith

November 13, 2012 at 8:14 am

3.1.28.3 seems to cause problems with overriding form styles from 3.1.27.

More importantly, 3.1.28.3 causes payments through Authorize.net AIM and SIM to fail. Based on the error message the authorize.net support person said it was because a non-alphanumeric character was being submitted in the item name or description.

I had to revert back to 3.1.27 to fix the issue.


Josh

November 13, 2012 at 8:34 am

Hi Chris,

Which forms were being overridden? Were these from the theme roller stylesheets of specific to your WordPress theme?

Also, 3.1.28.3 has added data sanitization to many of the forms, so if you had entered non-alphanumeric characters in the event name or price type, these will need to be re-saved so they get updated in the database.


Chris Smith

November 13, 2012 at 9:15 am

Josh, thanks for your quick reply.

The styles were on the registration form and we are using the theme roller style sheets.

I tried updating again to 28.3 and then re-saving my events, but it still did not work. Is there something else I need to do to re-save the DB entries?


Josh

November 13, 2012 at 10:05 am

Hi Chris,

Which theme roller style sheet option is being used? Are there older stylesheets copied over to /wp-content/uploads/espresso/templates? We’ve recently added a base stylesheet, and there may be a few conflicting style rules that we didn’t see in testing, and there may be some style rules from the theme that are affecting this. What is the WordPress theme that is being used? Can you send a link and a few details of what is conflicting?

With the Authorize.net issue, which alphanumeric characters are being used and where are they entered? If I can recreate this on my dev site, we can possibly narrow down what is causing the issue with authnet.
Viewing 3 reply threads

The support post ‘EE Update 3.1.28.3 errors’ 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

Notifications

This topic is: not resolved
Event Espresso - Staging Server