[Nico]

Super, remember to let me know when you have a chance to test it!

Best,
Nico

[Nico]

Oliver,

Thank you 🙂

I’ll go ahead and close out this thread, but if you need help with anything else please don’t hesitate to create a new one and we will be happy to assist you.

Have a great weekend yourself,
Cheers,
Nico

[Nico]

This reply is private.

[Nico]

Hi Keira,

Thanks a lot for following up on this, and sorry to hear we are still stuck with this 🙁

We’ve heard of different performance issues in the past, which are usually present in the front-end of the site -slow page views mainly. Some of them are due the high volume of events -mostly recurring-, in these cases using a cache solution or scaling the server infrastructure to a more adequate one. Do you consider that your actual server is up to the site growth? I’m not blaming your hosting company, just want to make sure you understand this can be a cause of the issue!

Before considering this a performance issue, I would like to fully discard conflicts with other plugins of the theme itself. Can you please follow the steps described in our Testing for conflicts guide? Maybe this could be tested in a development or staging environment?

Please let me know,
Best,
Nico

[Nico]

Hi Diane,

Thanks for following up on this once again, and also thanks for testing this without other plugins active. Sorry to hear the behavior is the same.

I would like to insist on trying this with default theme -and if possible even without ACF-, we have heard of various unexpected issues while integrating The Events Calendar with Genesis framework theme’s. I know this is not always possible on production but, Do you have a staging or local copy of the site where we can test this extensively?

Hope we can make this right soon,
Best,
Nico

[Nico]

Hi gcaottawa,

Thanks for following up on this. I’m glad to hear the code provided did the trick, sorry for the miss understanding – from your original description I understood you needed to remove the box from all events.

Regarding tickets visibility in the Shop page, just go to WP-Admin > Products > Edit the desired ticket. Just above the ‘Update’ button you’ll find the option ‘Catalogue visibility’, per default it’s set to ‘Hidden’ for tickets. Change this to ‘Catalog’ or ‘Catalog/Search’ to make the ticket visible in your Store.

Please let me know if you need help with anything else,
Best,
Nico

[Nico]

Hey Caroline,

Thanks for following up on this! A crude but quick way of solving this might be to include the initialization JS code just after the slider html. That should work I guess.

Other option could be to listen for the ajax call and once it loads fire the slider code. Unfortunately the coding for that customization would be out of our support scope. Hopefully the folks behind Royalslider might point you in a right direction also.

Please let me know if they come back to you,
Best,
Nico

[Nico]

Oliver,

Super stocked to see where finally getting down to the solution for this 🙂

I think waiting for the update is good idea, hopefully it will get things fixed. It will replace all the files so if the plugin installation was corrupt in same way this will most probably fix it. We are expecting version 3.12 to be out next week, so if you could hold on that would be great.

We can keep this thread open until you have a chance to update the plugins and confirm this fixes your issue.

Cheers,
Nico

[Nico]

Hey Oliver,

Great to hear the snippet worked as expected 🙂

You can take a look in the fix PR for this: https://github.com/moderntribe/the-events-calendar/pull/291. Bear in mind this will be part of the upcoming release, coming out most probably next week.

Thanks once again for reporting this! You rock!

Please let me know if there’s anything else I can help you with,
Best,
Nico

[Nico]

Hi Caroline,

Thanks for reaching out to us! Hopefully I can help you out setting this up 🙂

Looking into your site the issues seems pretty clear, when the events are loaded the slider html gets loaded again but it’s the javascript init code just runs once (on page load). I see two ways of fixing this: one is move the slider html out of the events block so it doesn’t get reloaded when events are paged, or trigger the slider init code every time the slider it’s included. This is the plugin init code:


<script id="new-royalslider-init-code" type="text/javascript">
jQuery(document).ready(function($) {
$('.new-royalslider-2').royalSlider({template:'default',image_generation:{imageWidth:'',imageHeight:'',thumbImageWidth:'',thumbImageHeight:''},thumbs:{thumbWidth:96,thumbHeight:72},autoPlay:{enabled:!0,delay:5000,stopAtAction:!1},visibleNearby:{enabled:!0,centerArea:0.5,center:!1,breakpoint:500,breakpointCenterArea:1,navigateByCenterClick:!0},video:{autoHideBlocks:!0,forceMaxVideoCoverResolution:'standard'},width:'100%',height:'400px',autoScaleSlider:!0,autoScaleSliderWidth:4,autoScaleSliderHeight:1,slidesSpacing:0,imageScaleMode:'fit',imageAlignCenter:!1,controlNavigation:'none',arrowsNavHideOnTouch:!0,loop:!0,numImagesToPreload:3,keyboardNavEnabled:!0});
});
</script>


Does this makes sense to you? Do you think you can tweak this or still need help?

Please let me know about it,
Best,
Nico

[Nico]

Hi Stefania,

Thanks for reaching out to us! Hopefully I can help you with this one 🙂

First of all I would like to make sure this if this is caused by WooTickets, by the snippet or by a combination of both. So can you try to remove the snippet and then try to access the preview of posts and pages? If it still doesn’t work please deactivate WooTickets extension and re-test.

It’s also worth trying the steps described in our Testing for conflicts guide. This way we can see if this is a problem in our plugin or a conflict with the theme or other installed plugins.

Regarding the “Include events in main blog loop” issue, Can you please open up a new topic for it? That way it can be addressed by another team member simultaneously by another team member.

Please let me know about the test results,
Best,
Nico

[Nico]

Hey Samuel,

Glad to hear you could set that fix up 🙂

I’ll go ahead and close out this thread, but if you need help with anything else please don’t hesitate to create a new one and we will be happy to assist you.

Cheers,
Nico

[Nico]

Hi Stacey,

Thanks for following up on this! Unfortunately we are not allowed to login into customer sites and make changes 🙁

Is there a way of seeing the actual html code that get’s into the app? Maybe an alternative URL?

Have you tried contacting AppPresser support on this? I’m not sure at all about where this issue might be coming from.

Please let me know,
Best,
Nico

[Nico]

Hey Oliver,

Can you access the server error log maybe we can find a clue in there? This still seems to be pretty random!

Another thing that might be interesting to take a look is the plain data on the data base, because it’s showing different dates in the backend events list and in the backend details. I see two options, maybe the information is not getting correctly saved or this is just a display issue.

Let me know if you can take a look at this, if not I can craft a little snippet to print this out,
Best,
Nico

[Nico]

Hi Oliver,

Oh, thanks for clarifying that. This feature is not deprecated, but you’ve discovered a bug in it!

There’s an encoding issue in the link for the ‘Merge Duplicates’ button, that’s why it doesn’t work. Take a look:


Actual link - wrong: wp-admin/edit.php?post_type=tribe_events&_wpnonce=b3dbee92de#038;page=tribe-events-calendar&amalgamate=1
Correct link: wp-admin/edit.php?post_type=tribe_events&_wpnonce=b3dbee92de&page=tribe-events-calendar&amalgamate=1


There’s an encoding issue after the _wpnonce value, hopefully if you change that manually and execute that URL, it will work. When this runs it sets the option ‘organizer_venue_amalgamation’ to 1, which prevents the button from showing up again. So if you need the option to be visible again just reset the option value, you can do by adding this code to your functions.php file:

add_action( 'admin_init', 'reset_amalgamator' );
function reset_amalgamator ( ) {
$events = Tribe__Events__Main::instance();
$events->setOption( 'organizer_venue_amalgamation', 0 );
}


This code will run every time you access the WP-Admin area, so just add this when you need to reactivate the button!

Thanks a lot for reporting this bug, a fix for this will be included in the upcoming release, which will see the light next week or so 🙂

Please let me know if you can run it manually for now,
Best,
Nico

[Author]

Posts