Enonic version: 7.4.0
OS: os x
When I use a date from content studio as a parameter in the
new Date() constructor, it fails when the timestamp has more than three milliseconds integers.
This timestamp will create a new date object:
This timestamp will fail to create a new date object:
The (new?) standard format for
published.from are now 6 integers long, which will also fail when used as argument in
I am not sure what I can do or should do. Is there a way to configure content studio to only use 3 integers, or do I need to update anything, or do I need to write code to remove the integers, or is it a bug?
I guess the main problem might be the Nashorn version doesn’t support those timestamps.