Hi OldGrumpyDE,
the plugin doesn’t include an own jQuery version. It uses the one provided by your WordPress installation.
Could you provide a link to your page? Probably another Script or plugin is replacing the WordPress jQuery version with a different one or even worse just includes another one on top, while not using the strict mode.
JP
Hi JP, “the plugin doesn’t include an own jQuery version” is exactly my problem. 🙂 Unfortunately, the theme I have to use comes with 5 (yes, FIVE) required plugins and I can’t switch to another theme – one of those plugins (or the theme itself, I still need to dig through it) loads jQuery improperly, making shariff fail to display at all. I can fix that by replacing the shariff minimized libs in the wrapper with the “full” shariff libs which include their own jQuery version.
However, I just noticed that clicking through still fails, doh. I can setup a test site for you if you want to have a look, just let me know where to send login credentials. I can only work at the live site during nighttime. 😉
Hey,
yeah, I know what you mean. Sometimes you are just stuck with what you have.
If you can set up a test site, I’ll take a look at it and maybe we can find a solution together.
You can send the credentials to: shariff (at) posteo.de
JP
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
You can send the credentials to:
Please don’t.
*Drinks coffee*
Please don’t.
Note that I’m not accusing anyone of ill will or bad intentions. But asking for credentials to get access like that is really discouraged.
Please don’t do that: when you offer to get admin access and/or FTP access then you’re really going to far and that’s not cool.
http://codex.ww.wp.xz.cn/Forum_Welcome#The_Bad_Stuff
Unless you willing to take responsibility for that user’s installation for now one (and they should NOT let you do that) then please do not ask or suggest that someone provide you those admin or FTP details.
You can provide assistance here, ask for log data, you can make recommendations and even suggest changes. But do not seek login access. That’s just going too far.
We are talking about a test site, not a productive environment or any admin / ftp logins. A test site should never be available without any kind of simple login.
Jan, thanks for your valid concerns. I probably shouldn’t have posted it that way, and I second your thoughts that it’s a bad idea in general. But in this case it’s about tracking down an issue between seasoned developers in a most convenient way. Rest assured, the test system is all locked up and closely monitored. Violators will be wrist-slapped or eaten by a grue as appropriate. 😉
In other news, I fixed the problem by beating the stupid $(…) out of the code and replacing it with the correct jQuery(…) – it’s working now. If you want a detailed elaboration why you shouldn’t use the $() shortcut in WordPress plugins, here is an interesting article about it: http://devotepress.com/wordpress-coding/how-to-properly-use-jquery-scripts-in-wordpress/
The problem occurred because the shariff wrapper wasn’t the only member playing “foul” here, there are at least half a dozen instances of $() usage spread across the eco system in question. I also filed a comment for the theme developer, hope dies last, you know. 😉
Sorry that it took me a while to get back to you.
Actually this issue was fixed quite a while back, by the original developers from Heise.
https://github.com/heiseonline/shariff/commit/96a75e0adef7414fd56cd358055a4124646d32d3
What version of our plugin are you using and are you sure that you are using our plugin and not the other one? Also a link to your site might help me identify the problem.
