Home › Forums › Calendar Products › Events Calendar PRO › JS errors from TEC on an individual event template
- This topic has 19 replies, 3 voices, and was last updated 11 years, 12 months ago by
Barry.
-
AuthorPosts
-
March 7, 2014 at 1:46 pm #116306
Jonathan
ParticipantHello,
We are seeing two JavaScript errors on our individual event pages only. We referred to this post: https://tri.be/support/forums/topic/plugin-conlict-js-errors-from-tec-front-end-acf-form-on-an-event-template/
And added the code here: http://pastebin.com/P6HqshtD to our theme enqueue file, which did not resolve the issue for us.
Our error states:
Uncaught TypeError: Object function (options){ /* Verify an empty collection wasn't passed - Fixes #6976 */ if ( !this.length ) { return this; } /* Initialise the date picker. */ if (!$.datepicker.initialized) { $(document).mousedown($.datepicker._checkExternalClick). find('body').append($.datepicker.dpDiv); $.datepicker.initialized = true; } var otherArgs = Array.prototype.slice.call(arguments, 1); if (typeof options == 'string' && (options == 'isDisabled' || options == 'getDate' || options == 'widget')) return $.datepicker['_' + options + 'Datepicker']. apply($.datepicker, [this[0]].concat(otherArgs)); if (options == 'option' && arguments.length == 2 && typeof arguments[1] == 'string') return $.datepicker['_' + options + 'Datepicker']. apply($.datepicker, [this[0]].concat(otherArgs)); return this.each(function() { typeof options == 'string' ? $.datepicker['_' + options + 'Datepicker']. apply($.datepicker, [this].concat(otherArgs)) : $.datepicker._attachDatepicker(this, options); }); } has no method 'noConflict'<br />
and this error:Uncaught TypeError: Cannot call method 'pro_tooltips' of undefined tribe-events-pro.min.js:8 (anonymous function) tribe-events-pro.min.js:8 c jquery.js:7341 p.fireWith jquery.js:7403 b.extend.ready jquery.js:6875 H<br />
We deactivated the ACF plugin, and renamed the local folder, yet these two errors are still showing up, so we do not believe it is a conflict with ACF at this point.Any ideas as to what may be causing these conflicts on our individual events pages only?
March 8, 2014 at 6:02 am #116456Barry
MemberHi – I’m sorry you’re facing difficulties here.
Can you give an example of a URL where I can see this issue? On visiting a couple of single event pages (and your main event pages) I saw no Javascript errors like the one you quoted.
Thanks for confirming š
March 10, 2014 at 1:29 pm #116924Jonathan
ParticipantThis reply is private.
March 11, 2014 at 7:56 am #117320Barry
MemberThis reply is private.
March 11, 2014 at 11:34 am #117426Jonathan
ParticipantThis reply is private.
March 12, 2014 at 6:06 am #117715Barry
MemberSorry for the confusion – there is a bug in our existing support tools that causes issues with private replies. Let me re-post:
Iām sorry I missed that first time, but thanks for clarifying (in Firefox, for whatever reason, this is not an issue).
I donāt see this same issue on a āstock installationā however so my guess is that there is a conflict going on here. Can you try these steps:
- Ensure The Events Calendar/Events Calendar PRO are up-to-date
- Deactivate all other plugins
- Switch to a default, unmodified theme such as Twenty Twelve
- Now test to see if the problem remains
- You could of course run through these steps in a testing environment so long as you can replicate the original problem there, too
If that resolves the issue, reactivate everything one-at-a-time until the problem returns: this should help to confirm if there is indeed a conflict and what in particular is conflicting if so.
Thanks!
March 12, 2014 at 7:18 am #117792Jonathan
ParticipantThis reply is private.
March 12, 2014 at 8:20 am #117863Jonathan
ParticipantThis reply is private.
March 13, 2014 at 9:45 am #118300Barry
MemberThis reply is private.
March 17, 2014 at 6:42 am #119712Jonathan
ParticipantSorry we cannot see your reply. It just says āThis reply has been marked as private.ā
March 17, 2014 at 9:11 am #119777Barry
MemberApologies again, re-posting:
There are definitely going to be situations where conflicts arise ā and thatās true of many different combinations of plugins/themes.
Something like Use Google Libraries, where you are not necessarily going to be using the same versions of fundamental libraries like jQuery as ship with WordPress, sounds to me like something that may be problematic unless you can guarantee that the exact same versions are used (as the WP default libraries). Depending on your theme, because coding standards vary, it could also lead to classic issues like two copies of jQuery being enqueued at one.
Iām speculating here ā but in honesty Iām not sure how much we can resolve without investigating each of those plugins one by one and getting a complete rundown of any applicable settings ⦠realistically, thatās pushing the sort of service we can offer.
(As a sidenote, please do try to avoid posting private replies unless you are sharing confidential information. Apart from triggering this issue with staff replies, which we’re working to resolve, it makes the information you are sharing – none of which is particularly sensitive – inaccessible to other users who might be researching the same topic.)
March 18, 2014 at 1:19 pm #120836Jonathan
ParticipantAs the conflict seems to specifically be with the datepicker, we tried disabling the javascript datepicker for the events plugin which did not solve the issue.
We then disabled the javascript datepicker via MailChimp, and we are still receiving the same 2 JS errors on page load.
Do you have any suggestions as to how we can bypass the datepicker on either both or one of the plugins?
March 19, 2014 at 9:09 am #121077Barry
MemberIs the remaining problem with āUse Google Librariesā and āMake your site socialā, then – and if so is it possible to explore alternatives to those?
April 3, 2014 at 6:25 am #127323Barry
MemberThis thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!
April 5, 2014 at 3:37 pm #128576jonathanhermandesign
ParticipantI have the same problem, but I noticed that both tribe-events.min.js and tribe-events-full.min.js load, as well as tribe-events-pro.min.js and tribe-events-pro-full.min.js. The difference is that the second js file has “full” in the name. If I use a http proxy to stop the non-full JS from loading, then I don’t get the errors mentioned by OP. And to clarify, jQuery is not loading twice, the problem is with the tribe-events js loading both the full and non-full js. Any way to fix this? Thanks
-
AuthorPosts
- The topic ‘JS errors from TEC on an individual event template’ is closed to new replies.
