Week View not working

[Dave]

Here’s a link to the problem on my website

I see another user has posted a similar problem (Week View is not working, why?) and has been told to update to version 3.12.5 to fix the problem. I have updated to version 3.12.5 and the problem persists.

In the Chrome Dev Tools console there are two error messages on the page. I took a screenshot in case that helps with de-bugging.

For the record, I have followed the steps described in your Testing for Conflicts guide, and detected no conflicts with the theme or plugins.

[Brook]

Howdy Dave,

Thank you for clearly detailing what you have tried. This is very strange, particularly for the problem to have persisted during a conflict test.

Could you try going to WP-Admin > Events > Settings and toggling “Recurring event instances”. Is it  currently on or off for your site? There has been some strange behavior surrounding this since 3.12.3 or so.

Please let me know. Cheers!

– Brook

[Dave]

Hi, “Recurring event instances” is off.

[Brook]

Thanks for the info Dave. I am sorry if I was not clear before, could you try toggling it to on? Does that change things?

• Brook

[Dave]

Hi, I toggled it, cleared my cache, closed and reopened my browser, but the events still don’t appear in Week View.

And I’m still getting the two error messages in dev tools. (You have included the Google Maps API multiple times on this page) and (Uncaught TypeError: Cannot read property ‘wheelDelta’ of undefined) I don’t know why the Google Maps API is being loaded, as I’m not calling it, and I have Enable Google Maps toggled off in the Events module.

[Brook]

Thanks for trying that Dave.

I’m definitely not ignoring those two errors, but I doubt they are related. They will almost without a doubt go away during a conflict test, but your real problem evidently did not. The only way you would see JS errors like that during a conflict test is if the plugin files became corrupted, which is extremely rare.

This is truly puzzling. We could try a couple of things here:

1. You could send us a copy of your database. I will then use that database to replicate your site on my test system, and see if I can reproduce the error. After reproducing an error a fix usually is quite easy.
2. Retry the conflict test, making sure to deactivate plugins and switch themes at the same time. In particular watch and see if the JS error goes away when you switch your theme. I understand if you don’t want to try this again though, you seem like a very thorough and methodical debugger so you probably have a high degree of confidence that the result will be the same.
3. Reinstall the plugin. Try deleting it from WP admin, and then redownloading and installing it.

Let me know which option you want to forge ahead with.

Thanks, Dave.

• Brook

[Dave]

Alright, to begin, thanks for sticking with me here.

I opted to start with option two; retrying the conflict test. This time however switching to the Twenty Thirteen theme caused the week view to start displaying events again. I don’t know if I missed it the first time around or if something I’ve changed in the meantime made a difference. I did update the base plugin (Events Calendar, not Events Calendar PRO) to Version 3.12.4 earlier this morning.

So to summarize, there is a theme conflict that causes the Week View to not display events. I’ve already checked the documentation for help to track down and fix the conflict but I haven’t found it yet. I did notice that the two warning messages went away when I had the Twenty Thirteen theme activated. There was a new third warning message this morning that came up and that one did persist. It was a yellow warning though, not red like the other two.
SensorNotRequired: https://developers.google.com/maps/documentation/javascript/error-messages

• This reply was modified 10 years, 5 months ago by Dave.

[Brook]

You are welcome Dave!

I am happy you gave that a whirl again. We would have ran down a lengthy road searching elsewhere. I debug all day long, but I also have to run the same test twice sometimes and will get a different result. :-/

Debugging a theme you didn’t write is unfortunately hard. Mostly because you have to rely heavily on your intuition/intimate knowledge of the APIs it uses and how it uses them. Bur if I were you, here is how I would start:

1. Dequeue the ‘tribe_events_google_maps_api’ script via wp_dequeue_script(). This should remove the duplicate API errorand maybe the sensor error.
2. Try dequeuing the scripts in your theme until all of the errors are gone. Then reenable them one at a time until you can isolate the remaining error. Then we might have a better idea of whats going on.

It seems like you have already found some way to get the events back though, as I am seeing them on your site right now in the current theme. That’s awesome! How’d you do it?

• Brook

[Dave]

Thanks for the advice and encouragement! I’m actually fairly new to this and so any advice I can get is very valuable. As I was comparing the working site (with default theme) with the non-working site (with Retailer theme) I think I narrowed it down to the sticky header somehow conflicting with the scrolling functionality on the Week View. So I tinkered around in what I felt was a fairly “hacky” (that’s probably not a real word) way, mostly in CSS but also by putting an altered week template into my child theme folder. It took a while but it’s working now and it does what the customer was wanting it to do, so I’m happy about that.

I’ll definitely do some research on wp_dequeue_script() and try using it as you suggested – it looks like a useful tool that I didn’t know about!

[Brook]

Excellent! You are very welcome for the assistance, Dave. Happy developing to you!

• Brook

[Author]

Posts