[Barry]

I’m going to go ahead and close this topic since it looks like your query was answered, Cristina 🙂 … if you (or anyone else) has any follow-up questions definitely let us know by creating a new topic.

Thanks again!

[Barry]

That’s a shame – I guess the cache cannot be built due to the timeout so it’s potentially helpful effects will not be able to kick in.

We’ll do our best to update you here in this topic once our proposed performance fixes are released 🙂

[Barry]

Hi Jessie – I’m sorry for the further inconvenience.

As above, we have logged a bug report for this and will address it as quickly as we can (and will also try to post an update in this topic once the fix is ready).

The work done in the 3.10 release had already been finalized at the point where we recorded this issue and, rather than delay getting those fixes and improvements out, we decided to address this problem in a separate follow-up release 🙂

[Barry]

Hi Jessie – we’ve got this logged and will address it as quickly as we can.

[Barry]

My pleasure 🙂

As you marked this resolved I’ll go ahead and close the topic – but definitely feel free to post new topics as required should anything else crop up.

Thanks again!

[Barry]

Great – and let me know if you have any further questions 🙂

[Barry]

Hi Samiaji,

I definitely see it’s a little less snappy than might be ideal.

With 12,000 events you may need to make use of caching (have you enabled month view caching, via the Events → Settings → Display screen) at various different levels to really squeeze the most out of available server resources – object and query caching in particular can be very effective.

Minimizing the number of events shown per day in month view is also a sensible step but it looks like this is already down to 3 events per day in your case, which is pretty reasonable.

All in all, caching is likely to be the best way forward here – though we do have some performance related changes in the pipeline that will roll out in a forthcoming release.

[Barry]

I suspect they may have an option that allows you to list certain assets that should not be minified – perhaps you could set up such an exception to prevent any assets belonging to The Events Calendar/Events Calendar PRO from being minified?

That way, you’d potentially still benefit from caching and minification in other areas without impacting calendar functionality.

(How exactly this works in W3TC isn’t something I can guide you through, but I’m sure the plugin docs cover this or else the plugin authors can offer you some guidance 🙂 )

[Barry]

Thanks Tony! We’ve now identified some issues that are likely to be contributing to this problem and are actively working on a fix.

[Barry]

Hi @pagan11460 – did you manage to clear things up? If there is still a problem definitely let me know 🙂

[Barry]

Hi @baynature,

Just checking in to see if you were able to troubleshoot further and if you discovered the source of the problem/need further help on this one 🙂

[Barry]

Hi Tim,

I’m sorry to hear you’ve hit up against some difficulties.

We do have a policy of sticking to one issue per topic, so let’s deal with the first problem in this topic and if you can create a new one for the second issue one of the team will be more than happy to help with that, too 🙂

1. For the month view, the listings don’t show as they do here: http://wpshindig.com/events/ (i.e. with the event title linked on the day of the event). Mine just shows a dot noting there is an event. http://gaychicmagazine.com/wp/events/month/

It looks to me as if The Events Calendar is being “tricked” into showing the mobile form of month view, even when this is unnecessary. In this case I suspect the problem is with the aggressive minification of Javascript and CSS assets implemented by your caching plugin.

I do see that when you opened this topic you noted having already tried our standard troubleshooting steps, which include deactivating all other plugins and switching to a default, unmodified theme.

When you ran through those steps, did you notice that this problem was fixed when your caching plugin in particular was disabled?

[Barry]

Hi there Wil,

Thanks for your interest in Events Calendar PRO 🙂

Beyond the setting (to only show the first upcoming recurring event) that you are already aware of I’m afraid there are no built-in tools to set up the sort of solution you’ve outlined. That said, the plugin is extremely flexible and you could certainly make this happen as a further customization if you’re up for some custom coding.

I hope that answers your question, but do let me know if I can expand on anything else.

Thanks again!

[Barry]

Hi Joel,

Almost anything is possible!

The best starting place for learning how to safely customize things is our Themer’s Guide, so definitely review that first of all if you haven’t already done so.

Please also note that the amount of support we can offer when it comes to custom coding is generally pretty limited so I may not be able to offer too much further help on this one, but if you do have further, more specific questions definitely let me know and if I can point you in the right direction I’d be happy to do so.

(It might also help to get some more information on exactly what you are trying to achieve, as right now I’m not absolutely clear as to the final outcome you’re gunning for 🙂 )

Thanks!

[Barry]

Hi Samiaji,

I see from the system information you shared (thanks for doing that!) that you upgraded from 3.9.3 – I’m curious, did the slowdown take hold after this update?

If so, we’re aware of some frontend performance issues that were inadvertently introduced and are actively working on a solution that we’ll roll out as soon as possible to resolve it.

[Author]

Posts