Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #25440

    There is an unusual “undefined” error that shows up on our pages. Quite literally, the word ”undefined” with no other information is in the header. I was able to track down this jQuery error: “Uncaught TypeError: Cannot read property ‘width’ of undefined ” using Chrome dev tools. Further digging shows a conflict with avia.js specifically the avia_menu_pointer starting on line 119. When that function is commented out, the strange “undefined” word goes away.

    Plugins, WP (3.5.2) and the theme (v1.4) are all up-to-date, but this issue has been present even before the theme update. I haven’t found any other inquires about this problem in the forums. Have you received any report of this error when that script runs? Any suggestions? Thanks!



    1) Maybe it’s a conflict with another plugin. Try to deactivate all plugins and check if the “undefined” error goes away. If yes activate the plugins one by one to find the culprit.

    2) If this doesn’t help try to re-upload all theme files. Maybe a file on your server is damaged or someone modified a file and the code modification breaks the menu function.


    Thanks for your feedback. We have isolated the issue to the Multiple Event Registration plugin, an important add-on for Event Espresso that allows users to register for more than one event/class/workshop at a time. With that in mind, we need to keep that plugin enabled.

    We’ve made numerous modifications to the theme, so I imagine that’s the issue, yet we can’t find a fix. Perhaps we don’t need the “pointer above menu” function at all. What exactly does that do? As a test, I commented out that entire function and the “undefined” error indeed goes away. Could you tell me the risks of NOT having that function running within the theme?

    Thanks again.

    Great themes and support at Kriesi.



    It only specify which menu item you’re currently on. Not a big deal. You can disable it if you want.



Viewing 4 posts - 1 through 4 (of 4 total)

The topic ‘avia.js conflict: "undefined" showing in header’ is closed to new replies.