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
Multiple Event Registration conflict: "undefined" showing in header | Event Espresso - Staging Server

Support

Home › Forums › Multiple Event Registration › Multiple Event Registration conflict: "undefined" showing in header

Multiple Event Registration conflict: "undefined" showing in header

Posted: June 26, 2013 at 7:22 am

Viewing 2 reply threads


Ariel Shanberg

June 26, 2013 at 7:22 am

We are unable to find a fix for an unusual “undefined” error that shows up on our pages. Quite literally, the word “undefined” with no other information is in the header, not only on our events pages, but also in most of our general information pages. When the Multiple Event Registration plugin is deactivated, the strange “error” goes away, but of course that breaks the event registration.

Tracing this leads us to believe there is a conflict with the MER plugin and jQuery. The only other error we can find is: “Uncaught TypeError: Cannot read property ‘width’ of undefined ” with Chrome developer tools. Everything is up-to-date including EE 3.1.33.3.P, MER 1.0.4 and WP 3.5.2.

I haven’t found any other inquires about this problem in the forums. Any suggestions?

Thanks for your assistance.

http://66.147.244.129/~cpworg/learn/workshops/event-registration/


Dean

  • Support Staff

    •

June 26, 2013 at 8:23 am

Hi,

Thats a strange one, certainly havent seen it before. The jQuery error is referring to jQuery itself, rather than another file so I cant pinpoint the issue right now.

Have you tested the site with all plugins EXCEPT Event Espresso and MER turned off? Im wondering if its a conflict between MER and a third party plugin.


Josh

June 26, 2013 at 9:25 am

I looked into this and I think it might be a script in the theme. If you look in the theme’s avia.js there is an avia_menu_pointer function that starts on line 119. It appears to be adding the markup where the undefined error is displaying. You might check with the theme’s support folks to see if they are getting any reports of the undefined error displaying when that script runs.
Viewing 2 reply threads

The support post ‘Multiple Event Registration conflict: "undefined" showing in header’ 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.

Status: closed

Updated by Josh 11 years, 6 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server