[Barry]

Hi Joanna,

We deployed a fix for what we thought was the core issue behind the problem you described just recently and some further Event Aggregator related fixes went out today 🙂

Can you confirm you are using the latest version of The Events Calendar and that you are still experiencing the problem?

Thanks!

[Barry]

Hi Ryan,

The fix already went out … can you confirm you are using the latest versions of The Events Calendar and that you are still experiencing the problem?

Thanks!

[Barry]

Hi Steph,

I’m really sorry to hear you’ve been disappointed by our plugins.

To stay focused on the caching issues first of all: it’s possible to mark specific sections of pages that otherwise ought to be cached as “dynamic”. This means that you still have the benefit of caching, but that smaller components of the page that need to stay fresh and up-to-date aren’t caught in the cache.

How this works (or if it is supported) depends on the caching solution you are using – but to give you an idea of how it basically works and what’s involved with popular caching solution W3TC, please view the following article:

http://www.justinsilver.com/technology/wordpress/w3-total-cache-fragment-caching-wordpress

I can’t seem to access your system information so I’m afraid I had to guess at the caching plugin – but, you can probably research this yourself by looking at the knowledgebase/any instructions provided with the actual caching plugin you are using.

On our side, if this means you need to customize some of our templates, you will find our Themer’s Guide to be a valuable resource:

theeventscalendar.com/knowledgebase/themers-guide

To mention a few things i am still having issues with, there are double entries from facebook imports, timezone resets to CEST whenever users update their submited events, no images on google calendar imports

I’m really sorry to hear that it has been a source of frustration for you.

I see you’ve created a number of forum topics besides this one — please do continue to post further topics for each individual problem you hit up against and we’ll do our best to assist you.

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

So we checked into this and, essentially, it seems like there is no reason for concern.

What you are seeing is simply a function of how many imports you have and the fact that the Event Aggregator client code breaks these down into smaller pieces (so, what looks like one scheduled import to you may actually be pulled in via several individual import operations).

It was certainly worth flagging this, but unless you are still seeing actual functional problems with imports not being pulled in as expected (if so, please provide specifics to better guide our efforts) I think we can put this to rest.

[Barry]

Re: imports, what I’m saying is I can literally see the plugin trying to pull imports like every other hour or on similar frequency – it never seems to stop making calls to try and import instead of running them at the scheduled times it’s supposed to. How do we stop this?

We’re taking a fresh look at this.

[Barry]

Looking at your license keys, you have business licenses but not multisite licenses.

Although we’re happy for you to use Events Calendar PRO on up to 3 sites (within a multisite network) using only a business license, automated updates are only available if you have a multisite license:

theeventscalendar.com/knowledgebase/multisite-license

With that in mind, you would need to update those plugins manually, unless of course you upgrade to multisite licenses:

theeventscalendar.com/knowledgebase/manual-updates

[Barry]

This reply is private.

[Barry]

Excellent, thanks for letting us know 🙂

[Barry]

Hi Christoph,

It’s been a while but since my last update here a number of fixes have been deployed on both our Event Aggregator server and within The Events Calendar itself.

How are things looking on your side?

[Barry]

Hi Scott,

A number of fixes have been released both on our own server and in the latest version of The Events Calendar. Especially with a few days having passed since that release I wanted to check in and see how things looked on your side.

It looks like perhaps you haven’t updated just yet (based on the readme data I see here) so I’d encourage you to do so, give it a few days and evaluate the status of things.

Thanks!

[Barry]

Thanks, Cliffy. We appreciate your patience while we looked into this and of course your continued support. Glad you managed to fix everything 🙂

[Barry]

Hi Scott,

Also, how do we fix the issue with imports not working so we can reliably count on scheduled imports that should be there to run? Still having to do everything manually..

This problem – being able to import manually but not via scheduled events – is very much the core issue and work is in progress to resolve this: a set of changes are currently being tested, in fact, and if testing is successful we can include them in the next release of The Events Calendar.

Thanks, challenge is we’ve got a calendar that’s still trying to auto-call hundreds of imports that haven’t been scheduled, how do we fix?

I’m aware of your earlier note that the history tab appears to contain more entries than you would expect in relation to the number of imports you have scheduled. Is that what you are referring to, here? If so, I’d again note that a 1:1 correlation isn’t necessarily to be expected owing to the way the system is built.

There may well be repeated entries in the history tab for the same source URL and they may appear more frequently than you would expect given the import frequency you set. In itself, that’s not necessarily something to worry about.

My recommendation is we wait on a fix for the core issue and then revisit this specific aspect if it continues to be a problem at that point.

This is a really long forum topic and we’ve covered multiple issues – but what I’d recommend from here on is that we dedicate this topic to the core issue (manual imports working, scheduled imports failing) and create separate topics for any other issues happening in parallel.

That will make it a lot easier to track and provide focused updates.

Thanks!

[Barry]

Glad it’s useful and that’s some great feedback 🙂

I believe the vision was that you could use this prior to editing a specific event (ie, only when needed) rather than trying to clean everything up en masse — which was something we explored, but there were a number of complications in doing so.

I’m afraid that it’s unlikely we’ll be able to roll out a further revision to this tool, at least in the immediate future, so while those are certainly worthy suggestions I can only recommend persevering with the plugin in its current form at this time.

[Author]

Posts