Photo View / Calendar Widget Conflict

[Big]

I’m using a highly customized them based on Roots (although I don’t believe this would affect this issue). I’ve added a sidebar within default-template.php and I can add any of the Tribe widgets to the Photo view with no problem. However, when I add the Events Calendar Widget, the events within Photo view are stripped of all classes except ‘isotope-item’. As soon as the widget is deactivated, the normal classes reappear (e.g., class=”hentry vevent type-tribe_events post-190 tribe-clearfix tribe-events-category-test tribe-events-venue-189 tribe-events-organizer-188 tribe-events-first tribe-events-photo-event isotope-item”). Obviously, this causes the events to lose all styling, but Isotope is still active.

(To make matters more bizarre, if an event is clicked, and then using the back button you return to the photo view, the javascript properly loads all of the classes and the page works as intended.)

I’m going to continue debugging, but if anyone has had a similar experience, or a better understanding of the AJAX and may know where conflicts would exist –- the help would be greatly appreciated.

[Barry]

Hi Big,

I can replicate something similar with Twenty Twelve so it doesn’t look like it is specific to your theme – what I did notice though is that this happens if the sidebar is called before the event view (in this case, photo view) is loaded – if it is called after this everything behaved as expected.

So, if it’s possible for you to rejig things to make it work by those means that could help you get on track faster – though I will definitely report this as a bug as I can’t think of any good reasons why you shouldn’t be able to do this.

[Big]

Barry, thanks for the response. I actually discovered that source order was the issue, so I’ve resolved it with floats – sorry, I should have updated his thread with that bit of info. I’ve also let Leah know about the issue, so it should be filed in your system. Again, thanks for the response!

[Barry]

Then we may have filed twice – it needs to be addressed in any case, so no worries. Glad you found a workaround 🙂

[Barry]

Hi Big: just wanted to let you know that we’ve been working on this issue and you should see some improvements with the next maintenance release, due to land among us in the course of the next week or so.

Thanks for your support and patience while we looked into this 🙂

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts