|
| Index | Recent Threads | Register | |
|
Forums » List all forums » Forum: Known Problems » Thread: mini calendar function -- jQuery error alert (front and backend of site) |
|
Total posts in this thread: 9 |
[Change thread status]
[Delete this Thread]
[Move this Thread] [Add To My Favorites] [Watch this Thread] [Post new Thread] |
| Author |
|
|
madison2
New Member
|
For site: http://www.madisonsquarechurch.org/, there is a mini-calendar feature in the 2nd footer widget. After the recent WordPress 3.6 upgrade, this site (out of a few dozen I manage) was the only one to exhibit the error alert message detailed here: http://wordpress.org/support/topic/wordpress-36-and-jqueryblockui-version-problem-solution?replies=22 -- and it is also the only WordPress site that uses Localendar, plus there are references out there to other calendaring widgets that experienced this same issue. Thus, I was able to narrow it down to Localendar, specifically the mini-calendar. The temporary "fix" for getting rid of that alert window was to comment out the following in the functions.php file: //Include script for mini calendar } ... as it was calling this: IncludeJavaScript('http://ajax.googleapis.com/ajax/libs/jquery/1.4.1/jquery.min.js');... which, to my limited knowledge of jQuery, is very bad. So, until you can issue a proper fix so that your code can peacefully coexist with the latest version of Wordpress, that mini-cal is rendered useless. Is there code I can/should replace the Googleapis reference with? Do you post another forum thread on this topic that I overlooked? Please advise! Steve C. webmaster, madisonsquarechurch.org |
|||
|
|
support
localendar Expert  Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
I'm not sure what leads you to say that... It's actually desired to pull the scripts from Google as they can serve them more quickly (see http://encosia.com/3-reasons-why-you-should-let-google-host-jquery-for-you/) And if you are concerned about the version.. different versions of jQuery can peacefully co-exist using the noConflict method (see http://stackoverflow.com/questions/1566595/can-i-use-multiple-versions-of-jquery-on-the-same-page) The thread you mention points out an issue with the jQuery BlockUI plugin and not jQuery itself. The issue you experienced is related to that plugin and not jQuery, the version, or the fact that it's hosted by Google. The issue is this bit of code in the BlockUI plugin: if (/1\.(0|1|2)\.(0|1|2)/.test($.fn.jquery) || /^1.1/.test($.fn.jquery)) {which has the bug mentioned in the thread you referenced (thanks, btw!) We haven't upgraded our WP test env for 3.6 yet, but we did remove the buggy jQuery check referenced in the thread (we can't just upgrade the plugin w/o testing against the variety of older WP versions where the localendar plugin is being used). Please let us know if that corrects your issue. ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||||
|
|
madison2
New Member
|
Ummm.... what is the "that" you refer to? Are we to find that plugin code ourselves, Localendar will be updating this soon, ... ? You state that it is within the BlockUI plugin -- where is that Plugin located? Please provide a more clear response & some clarification on who can/should do what -- if it is simply a matter of removing those 3 lines of code (or editing it?), then I can handle that, provided you detail for me its location. S |
|||||
|
|
support
localendar Expert Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
I'm not sure why you are being argumentative/trolling.
In case that's still not clear, let me reiterate that we removed the buggy jQuery code in the BlockUI plugin that was causing the issue. Check the plugin on your site. You don't need to do anything other than that. We are not upgrading the WordPress "compatible with version xxx" setting on WordPress.com until we do more testing. ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||||
|
|
madison2
New Member
|
Looks to be working again. Thanks - I wasn't trying to be argumentative - just couldn't decipher what it was you wanted (or didn't want) us to do from this end, is all... I got lost in the jargonese of jQuery and plugin development. Thanks again for the fix. |
|||
|
|
support
localendar Expert Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
Good to hear. Sorry to confuse things in my response. I just didn't want to promise a permanent fix until we run things through our internal tests. ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||
|
|
madison2
New Member
|
Looks like the error message is reemerging -- after a few days free of the alert window, some viewers are seeing it "come back", while others see it only in 1 browser over another. Still others (myself included) don't see it in any browser. Any thoughts? |
|||
|
|
madison2
New Member
|
Must have been a blip? Seems to have faded back away now again. Maybe a transition in the code you mentioned was adjusted from sandbox to live? Please keep us posted. |
|||
|
|
support
localendar Expert Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
No changes on our end. Most likely one of 2 causes: 1) Users' browsers cached the old javascript 2) Users' ISPs (or CDNs - content delivery networks) cached old versions and served these old versions to the community. You can't do a lot about #2 (except wait for the CDNs/ISPs to refresh their cache), but if #1 is the culprit clearing the browser cache should work. ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||
|
| [Show Thread Printable Version] [Post new Thread] |
Help! | Cobranding | Legal | Privacy Policy | About localendar.com | Contact Us |
