|
Yannis Develekos
|
September 28, 2013 at 1:54 pm
Hi there,
I’m using themeforest coworker theme and after installing Event Espresso, I guess there is some kind of Javascript conflict and it brakes functionality. Please, don’t try to visit diadima.gr, because you will visit our old website. You will be able to take a look at the new, WordPress website only if you add this line to your hosts file:
5.153.20.105 http://www.diadima.gr
[this editor keeps adding “http://” before http://www.diadima.gr. Anyway it shouldn’t be there]
There (www.diadima.gr), on the homepage, all the way to the bottom of the page, you can see that the client scroller and the testimonials scroller are not working anymore.
Any ideas?
Thank you in advance,
Yannis
|
|
Dean
|
September 30, 2013 at 1:18 am
Hello Yannis,
Do you have a publicly available version of the site? Or can you provide a screenshot of the console log to show us the error?
What version of WordPress are you using? What version of jQuery are you using?
|
|
Yannis Develekos
|
September 30, 2013 at 8:22 am
Hi Dean,
As said in my previous post if you add this line to your hosts file you will be able to visit the site. It’s fairly easy to do so. Anyway, how could I sent you a file with everything you need to debug my problem? Is there an email address available?
Thank you in advance,
Yannis
|
|
Josh
|
September 30, 2013 at 12:04 pm
Hi Yannis,
The problem is stemming from the theme not properly wrapping some of its functions in jQuery no-conflict wrappers. It looks like some of them are and some are not.
If you look in the theme’s custom.js file, there are a few functions that need addressing. The first one is the tab_widget function that starts on line 26 and later starting on line 573. They are all using the $ shorthand for jQuery and it’s throwing this error:
Uncaught TypeError: Property '$' of object [object Object] is not a function
This is a very common issue that comes up because Event Espresso (like many other WP plugins) is written to work in jQuery no-conflict mode.
While there is more than one way to fix this, the solution I like to use is outlined in this stackexchange thread:
http://stackoverflow.com/a/5382397
Another way to fix it is replace $ with jQuery within functions that are throwing the errors.
|
|
Yannis Develekos
|
September 30, 2013 at 2:58 pm
Hey Josh,
Thank you very much for your informative answer! Is it OK with you to forward your answer to the template creator?
Cheers,
Yannis
|
|
Josh
|
September 30, 2013 at 4:23 pm
Yes, and you can share with them this link as well:
http://digwp.com/2011/09/using-instead-of-jquery-in-wordpress/
|
