t = dateConvert( "utc2local", "January 1 1970 00:00" )
if BL is installed on a non english system. Even throws an error if I do a setLocale("English (US)")
before executing the command. So it seems to take the installed locale on the system.
I get this error:
The date time value of [January 1 1970 00:00] could not be parsed as a valid date or datetime locale of [Deutsch (Schweiz)]
(BL is installed in Switzerland)
Actually, the function should return a date time value of “[January 1 1970 00:00]”; ignoring the locale at all.
Found this issue using JWTTokens in the cbsecurity module method “toEpoch” of JwtService.cfc
Activity
Show:
Jon ClausenMarch 21, 2025 at 2:49 PM
Edited
This is resolved in the latest snapshot, however, you will need to specify the `en_US` locale in BoxLang if you want EN string formats to be parsed with textual values. Boxlang, by default, always considers the locale in date parsing and defaults to the machine locale - unlike Lucee and ACF, which are `en_US` locale-centric by default. This difference is very much on purpose.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
BL throws an error executing the command
t = dateConvert( "utc2local", "January 1 1970 00:00" )if BL is installed on a non english system. Even throws an error if I do a
setLocale("English (US)")before executing the command. So it seems to take the installed locale on the system.
I get this error:
The date time value of [January 1 1970 00:00] could not be parsed as a valid date or datetime locale of [Deutsch (Schweiz)]
(BL is installed in Switzerland)
Actually, the function should return a date time value of “[January 1 1970 00:00]”; ignoring the locale at all.
Found this issue using JWTTokens in the cbsecurity module method “toEpoch” of JwtService.cfc