Home › Forums › Calendar Products › Events Calendar PRO › JS error the events
- This topic has 7 replies, 4 voices, and was last updated 7 years, 4 months ago by Thomas Claffy.
-
AuthorPosts
-
November 5, 2016 at 10:58 am #1188218Thomas ClaffyParticipant
JQMIGRATE: Migrate is installed, version 1.4.1
tribe-events.min.js?ver=4.3.1.1:1 Array[1]
tribe-events.min.js?ver=4.3.1.1:1 TEC Debug: Browser and events settings information:
tribe-events.min.js?ver=4.3.1.1:1 Array[1]
tribe-events.min.js?ver=4.3.1.1:1 Array[1]
tribe-events.min.js?ver=4.3.1.1:1 Tribe JS Init Timer: 6ms
tribe-events.min.js?ver=4.3.1.1:1 Array[2]
tribe-events.min.js?ver=4.3.1.1:1 Array[1]
jquery.ba-resize.min.js?ver=1.1:9 Uncaught TypeError: Cannot set property ‘w’ of undefined
at m (http://myfergusoncalendar.com/wp-content/plugins/the-events-calendar/vendor/jquery-resize/jquery.ba-resize.min.js?ver=1.1:9:550)
at dispatch (http://myfergusoncalendar.com/wp-includes/js/jquery/jquery.js?ver=1.12.4:3:12444)
at r.handle (http://myfergusoncalendar.com/wp-includes/js/jquery/jquery.js?ver=1.12.4:3:9173)m @ jquery.ba-resize.min.js?ver=1.1:9dispatch @ jquery.js?ver=1.12.4:3r.handle @ jquery.js?ver=1.12.4:3
Navigated to http://myfergusoncalendar.com/
jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1
tribe-events.min.js?ver=4.3.1.1:1 [“TEC Debug: Tribe Events JS init, Init Timer started from tribe-events.js.”]
tribe-events.min.js?ver=4.3.1.1:1 TEC Debug: Browser and events settings information:
tribe-events.min.js?ver=4.3.1.1:1 [“TEC Debug: tribe-events.js successfully loaded”]
tribe-events.min.js?ver=4.3.1.1:1 [“TEC Debug: tribe-events-ajax-list.js successfully loaded”]
tribe-events.min.js?ver=4.3.1.1:1 Tribe JS Init Timer: 12ms
tribe-events.min.js?ver=4.3.1.1:1 [“TEC Debug: bootstrapDatepicker was just initialized in “tribe-events-bar.js” on:”, a.fn.init[1]]
tribe-events.min.js?ver=4.3.1.1:1 [“TEC Debug: tribe-events-bar.js successfully loaded”]November 6, 2016 at 7:16 pm #1188477HunterModeratorHi Thomas,
Welcome back 🙂
I imagine you’re already aware of our Testing for conflicts guide, so please review that and reply back with what you find out. I also notice you’re running outdated versions of our plugins. Please update to the most recent versions to see if that has any effect.
Once I have the results from the Testing for conflicts guide, we’ll be able to proceed. Thank you for choosing PRO and have a wonderful evening. Cheers!
November 7, 2016 at 6:19 am #1188576Thomas ClaffyParticipantThis has been going on for weeks. It happened when I was down to 2016 and no other plugins and your update did nothing to fix this. As usual, I get the no effort reply from you. The last item you handled for me resulted in a lecture on why you don’t bother to actually do anything about it because your code is infallible and it’s almost always someone else fault and then you closed the support item. I obviously can’t fix your code nor do I have any idea what is causing this error so if you don’t want to look at this perhaps you can pass it on to someone else?
November 7, 2016 at 1:12 pm #1188785HunterModeratorThomas,
I’m sorry to hear you’ve been experiencing the issue for weeks, but I’m not able to reproduce the behavior on my test installation using the default WP theme and our plugins. Unfortunately, conflicts that involve a custom theme and/or additional plugins are outside out scope of support.
To ensure I’m not missing something, I took a few minutes looking for relative bugs in our logs, but I’m not seeing anything. I understand how frustrating it can be in this situation, but I assure you if there was anything I could do, I would already be hard at work looking for a solution for you. We put these guidelines in place to maintain our brand. If we chose to take on every conflict our users had, we would be a completely different company.
If you can show me exactly what part of our plugin is causing an issue, I would be more than happy to try replicating the behavior and if I get the same results, a bug report will be filed. I hope I’ve clarified the reasoning behind our guidelines and let me know if you have any comments or concerns. Thank you for your patience and have a good afternoon.
November 27, 2016 at 11:59 am #1198022Thomas ClaffyParticipantStill happening daily along with the strtotime() error.
jquery.ba-resize.min.js?ver=1.1:9 Uncaught TypeError: Cannot set property ‘w’ of undefined
at m (http://myfergusoncalendar.com/wp-content/plugins/the-events-calendar/vendor/jquery-resize/jquery.ba-resize.min.js?ver=1.1:9:550)
at dispatch (http://myfergusoncalendar.com/wp-includes/js/jquery/jquery.js?ver=1.12.4:3:12444)
at r.handle (http://myfergusoncalendar.com/wp-includes/js/jquery/jquery.js?ver=1.12.4:3:9173)m @ jquery.ba-resize.min.js?ver=1.1:9dispatch @ jquery.js?ver=1.12.4:3r.handle @ jquery.js?ver=1.12.4:3[26-Nov-2016 21:32:51 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/myfergus/public_html/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 969
November 27, 2016 at 6:36 pm #1198077HunterModeratorHey Thomas,
I hope you had a great weekend. The errors you’re sharing with me don’t seem to be complete coming through. Feel free to share them via Pastebin.com. I’ll also need you to confirm whether or not the errors are occurring with the default theme and only our plugins active. If you’re unable to do this on your live site, it’s recommended you set up a test environment when you can fully troubleshoot the issue.
Thank you for understanding and have a great evening. Cheers 🙂
December 19, 2016 at 8:35 am #1207719Support DroidKeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘JS error the events’ is closed to new replies.