Multi-day events with start end has problems with date time separator am30 pm30

[michaelbuddy]

First off, note this happens on Multi-day events where specific start / end times are used. It appears to originate from the calendar settings, the date / time separator default is the @ symbol. I thought this looked bad so I changed it to ‘ at ‘ or ‘blankspace at blankspace’ . When you see the output on the event details page, on multi-day events, it replaces my ‘ at ‘ with am30 or pm30 in the output. I don’t understand why am30 pm30 are being processed there from nowhere. See example page: http://wustlcalendar.jumpserver.net/event/career-center-social-impact-career-week/ under the details section of this single page view, note the separator. These characters dont’ show if I use ‘@’ or even just a blank space as separator but not ‘ at ‘ Do you know why this field is unpredictable and if I have a way to get around it? (it occurs on my template as well as the default template fyi) [Update: I see the problem originates in that settings field or the output line is being translated to date time php format instead of accepting plain text.]

[michaelbuddy]

another update, I was looking at some PHP docs and thought maybe I could escape the characters ‘at’ so that the line wouldn’t be processed by the date time parser, but unfortunately it won’t work because using \a just creates a mess in the other views and doesn’t help anything in the detail view anyway.

[Josh]

Hello michaelbuddy,

Thanks for reaching out to us! I apologize for any inconvenience you’re having in using our plugin.

I tested this locally and was able to recreate the issue that you’re describing. I’m creating a bug ticket for our developers to review and look into addressing in an upcoming release. I’ll add this thread to the ticket and you’ll be notified of the progress as our developers work to address the issue.

Thanks!

[Leah]

Hi there,

I wanted to post here and update you. Although we weren’t able to get a fix for the issue your reported into our upcoming 3.9 release, it is still on our list to get corrected. Thank you for reporting the problem, and for your patience and support while we get a solid fix in place. We’ll update you when a solution is ready to go.

Best,
Leah

[Josh]

Hey,

We like to close out tickets after they’ve been inactive for a couple of weeks. If you have any further questions on this issue, please don’t hesitate to open a new ticket.

Thanks!

[Author]

Posts