Incorrect display of the year

[Eva]

Hey guys,

Since I activated the Community Add on I have a problem with the display of the year. It is always shown like that: 00000005 if the event takes place in may or like that: 00000008 if the event takes place in august. So the year correlates with the month..?

Here you can have a look http://kontextundverhalten.org/veranstaltung/datumstest/

I get the same wrong year in the notofication emails about a new submitted event.

Thanks for having a look at this issue!

Eva

[Barry]

Hi Eva,

So does this only impact events submitted through Community Events?

I do also note that you are using Enfold which ships with a number of customizations targeting The Events Calendar. Every now and again these can be a source of breakages. With that in mind, I wonder if you could do the following test:

• Please switch to a default, unmodified theme such as Twenty Fifteen
• Is the problem still apparent?
• Still with Twenty Fifteen activated, submit a new event through Community Events
• Is the problem apparent for this newly created event?

Thanks!

[Eva]

Hey Barry,

I tried everything but we have always the same problem. With or without Community Events (activated and deactivated), with Twenty Fifteen or with Enfold – for new created events its the same. I deactivated all other plugins – still there. And I realized that the year is missing when the event starts and ends at the same day. Please can you have a look at this too? The year should be displayed in every case.

Do you need any login?

Thanks!

[Eva]

Don’t know if this is important: I have seen in the settings that I have chosen for the datepicker formatting 15-01-2015, but its shown as 2015-01-15. Would be nice if this would work too 🙂

[Barry]

Hi Eva,

Let’s stick to the initial issue in this topic. If you need help with other problems please create additional topics (one issue per topic) and one of the team will be only too happy to help 🙂

If you visit Events → Settings → Display you will see a section called Date Format Settings – can you tell me what each of these is set to?

Incidentally, this sort of information can be shared easily in future topics by providing your complete system information. It looks like, for some reason, you deleted almost everything (or only copied a small piece of it) before providing it when you opened this topic.

Thanks!

[Eva]

Hey Barry,

What system information do you need? Sorry, I am not sure where I should have deleted anything…

The settings I have made are the following:

Date with year: d. F Y
Date without year: d. F
Month and year format: F Y
Format Weekday: D d.n.Y

And sorry for my other question. I thought it could be important for this issue.

Thanks

[Barry]

Hi Eva,

This is really quite odd: I haven’t seen any other customer reports of this and I am unable to replicate it, even with the date format settings you provided.

I wonder, do you have a test site or can you create one? It could be as simple as installing WordPress in a subdirectory at your existing domain (ie, http://kontextundverhalten.org/testsite) … if you start with a perfectly clean installation like that and activate only our plugins, do you still find this problem occurs?

Let’s try and get that far – of course, if you do still see the same problem (with nothing else activated) please let me know so I can take a look at the issue on the test site.

Thanks!

[Eva]

We found the problem: It was the separator between date and time. It makes problems if you add a word there.
But even if we format it like suggested in the wordpress codex (with slashes, e.g. \a\t or in German \u\m) it breaks.
We are using the @ separator now – that works.

[Barry]

Hi Eva,

That makes sense (and we actually have a bug report about this, so a fix should arrive and allow you to take advantage of escaping within date formats in an upcoming release) 🙂

[Leah]

Hi there,

Thanks again for your post. We wanted to get in touch and let you know that although we weren’t able to address this issue in our upcoming 3.10 release, it is still very much a priority. We have a ticket in our system and will be investigating a solution to be released in a future version. Thank you for your patience and support while we work on this!

Cheers,
The Events Calendar Team

[Leah]

Hello,

Thank you again for bringing this issue to our attention. We’re happy to say that we have added a fix for this into our upcoming version 3.11 release. Keep an eye on your Updates page for the new version. If you have any trouble with the update (or are still seeing this problem after you update) please start a new thread and we’d be happy to help out.

Thank you for your patience while we got this release ready to go!

Best,
Leah
and the rest of The Events Calendar team

[Author]

Posts