Timeline not interpreting YYYY-MM-DD format correctly (with Knightlab)

Hi!
I have an Omeka S site and I have recently installed the Timeline plugin, after updating to 4.1.1. I followed the plugin documentation and formatted my dates to ISO-8601 and adopted YYYY-MM-DD. However, when I load my timeline (Knightlab, not Simile), these dates are not interpreted correctly. Only years are. If I write 1535-10-03, it does not read 3rd October 1535, but 0000-01-01. The same for intervals that are not years: 1535-10-01/1535-10-31 is interpreted as 0000-01-01 as well.
According to the documentation, for the Knightlab timeline “Date should be ISO-8601, partial (“YYYY”, etc.) or full (“YYYY-MM-DDT00:00:00Z”)”, so that this should be supported. What could be the problem? The only conflict I can think about is with some locale, since the language is Spanish and in Spanish you use DD-MM-YYYY (or with / instead of -), but it seems higly unlikely. The other option I cant think of is that there is some problem with the servers, which tend to do strange things, lately, but it seems a too specific error for being the case. Does anyone know what could be happening?
Other functionalities of Timeline are neither working, whould this be of any importance: if I try to establish a group with a property (in my case: RDA has expression manifested), the timeline crashes and is not shown any more. I cannot either append more metadata to show.
Thank you very much in advance for your help.
Mylady

I have no familiarity with this specific module, but just in case, you may be interested in the fact that the mapping module also offers a timeline option.

See the documentation here and here.

Should this alternative fit your needs, be mindful that:

Note that this feature requires the Numeric Data Types module and at least one item that has a property with a Timestamp or Interval value (applied via the resource template).

1 Like

Thanks! I will keep an eye on this alternative solution. Luckily, if I just use the year, the timeline looks very much the same, but it would be better if I used full dates.
Although it is not stated anywhere, could it be that the Numeric Data Types module would fix the problem? I will give it a try.
All te best,
Mylady

Just in case someone is interested, the Numeric Data Types module does not solve this problem. Timeline is still not interpreting YYYY-MM-DD as it should.

You might try posting an issue directly on the module’s git respository. There is a link to in on the module page.