[Barry]

Hi yvrmark, what is your end-of-day cutoff setting?

If I have an event that runs past midnight but ends before the cutoff time, then it shows only on the first day.

[Barry]

Hi John.

It looks like you might have shared some code to help illustrate the problem, which is great … unfortunately the forum currently does a poor job of handling any code that’s been added to replies.

If you did indeed include a short snippet can I ask you to post again but share it via Pastebin, Gist or a similar service?

Thanks!

[Barry]

Hi Thomasek: this looks like a known bug which we hope to fix in an upcoming maintenance release. Thanks for your paitence while we work through this.

[Barry]

I’ll go ahead and close this thread. The problem you (Oliver) reported is on our bug tracker and ought to be resolved in one of our upcoming maintenance releases. Thanks!

[Barry]

Thanks Robin!

@Jonathan: the next logical step would be to go back to basics by ensuring The Events Calendar and Events Calendar PRO are both up to date (it looks like they are), deactivating all other plugins and switch to a default, unmodified theme – then see if the problem still persists.

This might help to isolate a conflict. I do appreciate you remarked earlier that this is a tricky process for you to follow, so I’d recommend either doing it in a period of low traffic levels or else within a duplicate environment.

If you have further issues along these lines after having followed those steps please do create a new thread of your own (as your issue is, it turns out, quite different from what the original poster – Robin – reported).

Thanks!

[Barry]

It needn’t require changes to core code: our own event queries are themselves based on WordPress’s own query mechanism and simply makes use of filters to modify it. By extension, you too could use the same group of filters and make additional tweaks.

You can get an idea of what’s happening in:

the-events-calendar/lib/tribe-event-query.class.php

Hope that helps! I’ll go ahead and close this thread now as we can’t help any further with customizations like this one, but we do wish you luck 🙂

[Barry]

Good catch Michelle, I didn’t actually notice that in your list of plugins – apologies for missing it. Unfortunately, yes, that does conflict with our events plugins (the reason being that they too include it – but it cannot be included more than once without causing a problem).

So, for the time being, the best I can suggest is keeping that plugin deactivated (we are aware of this conflict and are looking into a possible fix for the future).

[Barry]

OK. I suspect somewhere along the line an error is being introduced (perhaps you are passing the code through something other than a text editor, are including line numbers or are appending it / not completely erasing the previous code?) but the same fix certainly seem to work without issue locally – and has done for other users, too. Unfortunately I’m not sure we can help much further in guiding you through patching this – but do know that this will in any case be resolved in the very next maintenance release.

As I don’t think we can offer much more here I will close this thread, but of course if there is anything else we can help with please do create new threads as needed.

Thanks!

[Barry]

Yes you’re absolutely right, sorry for the confusion.

Within those views the address is indeed passed to Google (whereas map view itself uses the coordinates). It should definitely be consistent and it seems sensible that we use coordinates for both – so I’ll make sure this is logged as an area in need of attention.

[Barry]

Hi Peter: I only see the Dropbox link you previously shared (and that still provides a copy of Events Calendar PRO rather than your theme) – there are no other suitable links that I can see in your above posts.

[Barry]

Hmm, can you try replacing the same file as before, but with this version of the code? I do see a difference in terms of whitespace that might cause the code to be interpreted differently by different runtimes – but otherwise it should do the same thing (and resolve this error).

If it doesn’t resolve this then I would wonder if you have some form of (opcode) caching in place on your server that isn’t invalidating quickly enough.

[Barry]

Thanks, Stéphane.

In this specific case though, it might be a good idea to add one as most users who are not coders would struggle even more than I did to change that date display.

That’s a fair point and I will log this for consideration – I can’t make any guarantees but we’ll certainly review this in light of your comments.

A suggestion about your docs if you don’t mind. It might be a good idea to add examples like this in there … I find your docs have little in terms of usable or directly applicable details, at least in the areas I looked at.

We agree: as it stands, it certainly has its shortcomings and do wish to keep building and improving this side of the project. Bear with us though and overtime I do hope you will see further improvements in the depth, quality and range of our documentation and also supporting resources such as our tutorials.

Thanks again and good luck with your site 🙂

[Barry]

To be clear, which map are you referring to – the main map as shown on map view, or on other pages (single event/venue)?

[Barry]

That’s unfortunate.

The basic process for updating manually though is to either use WordPress’s own tools for uploading a plugin in .zip archive format (visit Plugins → Add New → Upload) or else you could unzip the plugin locally then upload it by FTP, overwriting the existing plugin.

Please do:

* Backup first of all
* Make yourself aware of how to restore that backup
* Consider putting your site into maintenance mode using a suitable plugin while you update things

I hope that helps!

[Barry]

Which of the snippets in that thread are you using (I see there are two, one that we suggested and one provided by WooThemes support)? Essentially though it sounds like something that you would need to customize a little to get a nice fit.

My understanding is that this is effectively a bug in WordPress itself and, unfortunately, one that won’t be fixed.

[Author]

Posts