Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect date (year) stored for a reply #4461

Open
Dunceantix opened this issue Jan 7, 2025 · 3 comments
Open

Incorrect date (year) stored for a reply #4461

Dunceantix opened this issue Jan 7, 2025 · 3 comments

Comments

@Dunceantix
Copy link

Dunceantix commented Jan 7, 2025

Hi,

I have seen a bug where the date is wrong. All other dates in the system before and after seem fine except this one entry and I don't know what could have caused it.

image

image

The first image is my reply to a customer, and then they replayed back a few days later, but for some reason the sysem has set the date to Dec 29th 2025.

image

This is the email from the actual mailbox itself.

I have other support requests from both before and after this occured which are all correct.

PHP version: 8.2.20
FreeScout version: 1.8.157
Database: MySQL (MariaDB)
Are you using CloudFlare: No
Are you using non-official modules: No

@bxschmidt
Copy link

bxschmidt commented Jan 8, 2025

We had the same problem. The issue is the difference between lowercase and uppercase "y"/"Y" in date format string on change of year. Seems to be only a display issue.
For carbon uppercase Y is year of calendar week which leads to the issue.

@Dunceantix
Copy link
Author

Ah yes, I have also found it in other places in the interface like on the spam filter list:
image
I think it appears on any tables where there is a date column of some sort as I'm also seeing it on "sent", "mine" etc

@freescout-help
Copy link
Collaborator

Fixed in the master branch and will be published in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants