Hi, does this issue persist for you today? I've been trying to replicate this to no avail so it was either temporary or it has to do with Safari maybe?

Hello, I can confirm I just had this issue. In my case, what I did was:

1. Edit an event
2. Click on Articles & Worlds
3. Click back on Timelines
4. Edit the event again

This needs to be done quickly to reproduce. What it looked like for me was like it takes time for the Timeline to update the changes and so, if the user hits edit before it has time to update, it will lose the changes.

For me it's just doing anything with Timelines that is not saved. Nothing. Not even when waiting a long time.
But I also never see the saving icon. So maybe the changes are not saved at all?

Using Chrome and Firefox alike on a Windows machine.

Edit: A few minutes later i discovered, that when reloading the website it has saved everything... But still something that needs fixing.

Same here as of 4/2. Nothing in timelines is saving.

I am also having this issue. Reloading the page does seem to recover data, but if you edit an event, click off, then click back to that same event it returns to a default configuration. Issue is easily repeatable. I am using the new time line style in "List" mode on Firefox Windows 11.

Encountering this issue as well. I left the timeline a few weeks ago because it wasn't saving at all, came back today hoping it had been fixed. Had me create a whole new timeline because my previous one wouldn't even open; the new one seemed to be fine and said it was all saved, and eventually even saved the custom era abbreviations (it erased them a few times, I waited longer before swapping and it said it saved). Then when I went to another article to edit that and came back, same thing. Won't even open the timeline I'd made fifteen minutes ago. Using Ecosia on a macbook air. 4/16

I have the same bug. I can create new events, but can't save any changes on eras or events. I use Opera on Windows 11.   EDIT : it looks like it works on Chrome, and my edits were there. Looks like it's a browser problem for me.