Upgrade Breaks Event List Navigation

[Mad Dog]

I upgraded tonight to TEC 4.07, Pro 4.07 and Community Events 4.05. Now when I go to Event List or Grid (the two views we use) and I use the navigation at the bottom to NEXT EVENTS I get the greyed screen, loading icon…..forever. Ajax screwy maybe?

I tried Chrome, FF, and IE and all have the problem.

I may see the problem…..your Release Notes says Community Events should be 4.06 but that didn’t upgrade and I can’t get that version in Downloads either!

MD

[Brook]

Howdy MD,

I am happy to help you with this. I can see the same problem on your site. In inspecting the ajax response I am noticing a PHP error that is preventing it from properly responding:

Warning: Invalid argument supplied for foreach() in /home/bhaddad/public_html/THAI/wp-admin/includes/plugin.php on line 1445

Warning: Cannot modify header information – headers already sent by (output started at /home/bhaddad/public_html/THAI/wp-admin/includes/plugin.php:1445) in /home/bhaddad/public_html/THAI/wp-content/plugins/the-events-calendar/src/Tribe/Template/List.php on line 137

I bet that error stems from the function remove_menu_page() in WordPress. Do you remember using that anywhere on your site, perhaps in a modification to The Events Calendar or your theme? If so I would start there, see if after examining the code you know why it’s causing errors now. Feel free to share that code here and I can help.

If you don’t recall using that function anywhere, and the above error message isn’t helping, then we’ll need to do a standard conflict test to zero in on what is conflicting with the latest version. This guide walks you through how to test for a conflict, and then identify what is conflicting.

I may see the problem…..your Release Notes says Community Events should be 4.06 but that didn’t upgrade and I can’t get that version in Downloads either!

That is totally our bad. I am sorry, that version was not yet released even though it’s in our release notes! A bit of an odd scenario. Our team wastrying to release those versions just prior to us all heading out for a team retreat, and it seems this slipped through the cracks. I’ll let you know once that version of Community is released proper. In the mean time though your site should continue functioning without error, the old version of Community you’re running is compatible with the latest versions of everything else.

Cheers!

– Brook

[Mad Dog]

Thanks for checking on that. I looked and hadn’t used that function. Then I remembered I use a plugin called WP Admin No Show in order to keep a role from getting to the admin page. So I deactivated it and all is good. Oddly, when I reactivated it just to test….it’s still good. So perhaps it reset something.

Lord only knows…..another update, another glitch. Luckily minor this time!

THANKS

[Mad Dog]

I spoke too soon. It’s doing it again. That’s really wacky.

I need to do a bit more troubleshooting……

Here’s a question, I don’t know if you can answer though….it worked fine all along. Any idea what may have changed in the newest updates that could be causing the conflict?

[Brook]

Howdy MD,

Hey we’re getting somewhere, that’s good news.

I am not exactly sure what change would impact this. You can see a complete list of changes here. Nothing on that list would have an impact that I can see. :-/ Many of the new files just have to do with automated testing, a feature that’s not even included in the .zip version on your site, because you don’t need testing files for a live site. I wish I could be of more help there. Maybe you’ll see something in the list I missed?

• Brook

[Mad Dog]

This is going to take some sleuthing because it’s been intermittent. I installed the new Community Events update last night and checked and it worked. I figured the had changed or fixed something. This morning…no luck. Page Inspector isn’t showing any js or other errors which is what’s really strange to me.

Weird….

[Mad Dog]

Testing some things, I’m seeing a possible pattern that makes no sense to me. I turned on WP DEBUG and one plugin was showing up in particular. So for yucks, I deactivated it. The Next Page Ajax works. So I activated the plugin again and the Next Page still works.

I had the same thing the other day when I deactivated a different plugin. Things worked, then continued to work when I activated it again.

For a while. Then it stopped working.

Now…I just tried another browser (FF) and it’s not working. The Loading graphic is just spinning.

Does this make any sense to you? It’s almost as if something is resetting in the browser when I deactivate a plugin but I have no idea what…or if it’s just a fluke.

Any ideas?

THANKS

P.S. In FF I turned on Firebug. No errors. I try Next and it works…..!? W…T…F…?

[Mad Dog]

This reply is private.

[Brook]

Howdy again,

Thanks for your patience with us this past week. We’re all catching up on the backlog right now and should be back to business soon. 🙂

Clicking Next gives me the same error as before, line 1445.

Do you have Debug Bar enabled? That could be part of it. Debug bar will often suppress mid page errors for logged in admins, moving them to its console. So if you tested an ajax request like the Next button with Debug Bar while you’re logged in it very well might work. But while logged out or with Debug Bar off, it will generate the Ajax halting error again.

Let me know how I can help!

– Brook

[Mad Dog]

Hi–

I didn’t know what Debug Bar is until I just looked it up (I assume it’s the WP plugin). Here’s what I’ve just discovered: it works when I’m logged in as an admin but not otherwise. I’ll check Debug Bar and your finding way up top of this thread and see what I can find.

Does the “works when logged in” give you and clues you can pass along?

Thanks
MD

[Brook]

Not really I’m afraid. Many plugins treat things differently when you’re logged in, so that does not help narrow it down much. I think our best clue at this point is the remove_menu_page() function. And since you’ve narrowed it down to having to be logged out, that helps too. I’d continue your conflict testing while logged out and see if it becomes more consistent.

Sorry its such a pain. I wish there was more I could do from my end. Likely any plugin that uses the WP Ajax API is broken right now on your site, which of course includes ours.

• Brook

[Mad Dog]

The usual long, gory testing found the culprit: the Nivo Slider plugin.

Now…I know you don’t support other plugin conflicts, but any leads on where to look? Unfortunately I need both plugins!

Thanks,
Mad Dog

[Brook]

Howdy MD,

Thanks for reporting back.

I’m not familiar enough with the Nivo slider plugin to offer good alternatives. But now that we know where the conflict is coming from we can reach out to them directly. We will start by offering them free licenses/support for our plugins, and seeing if they wouldn’t mind doing something similar. If so we can test this issue until we can reproduce it, and see if a fix should be crafted for our plugin or theres. Eventually an update can be release for one plugin or the other that addresses things. But this is unfortunately usually a bit of lengthy process, given working with two different teams and various schedules.

Thanks again!

• Brook

[Mad Dog]

It’s fixed. Looked deeper and noticed that the Nivo Slider plugin was outdated and because they changed the way they handle support etc, there was no notification that there was an update. I updated and it seems to be good now.

Whew!~

Thanks for the guidance and patience working through this.

MD

[Brook]

It’s been my pleasure. That is really good news! Thank you very much for updating me on this.

• Brook

[Author]

Posts