Skip to main content ↑ ↓
Topic: --human date-- with future dates beyond 2038 (Read 1383 times) previous topic - next topic

--human date-- with future dates beyond 2038

Found that any future dates beyond 2038 return 'Bad Date'

Looked into the function code and found you are using UNIX signed 32bit integer.

The latest time that can be represented in Unix's signed 32-bit integer time format is 03:14:07 UTC on Tuesday, 19 January 2038 (231-1 = 2,147,483,647 seconds after 1 January 1970).

Also, would be nice to add custom date format from PHPRad studio, as well as custom formats for currency - like no decimal places, and commas for ,000

Re: --human date-- with future dates beyond 2038

Reply #1 –
Thanks for the great observation. Any idea how we can solve it as this is PHP limitation.
Also which other date formats do we need to support?

As for the currency format, I. You can set the FormatRecordField for any currency like:

Code: [Select]
--to_currency('en-GB')--
--to_currency('en-US')--
--to_currency('it-IT')--

Ouput something like :
£406.00   $406.00    406,00 €  


Best Regards

Re: --human date-- with future dates beyond 2038

Reply #2 –
Quote from: Emman –
Thanks for the great observation. Any idea how we can solve it as this is PHP limitation.
Also which other date formats do we need to support?

As for the currency format, I. You can set the FormatRecordField for any currency like:

Code: [Select]
--to_currency('en-GB')--
--to_currency('en-US')--
--to_currency('it-IT')--

Ouput something like :
£406.00   $406.00    406,00 €  


Best Regards


What is the format for the Portuguese Brazil?
DougBack