Switching back from :unstable tag to :latest tag breaks website

[inuonly]

Description

Earlier to test one of the UI issues which was resolves by one of the vikunja team members, we switched from latest tag in docker image to unstable tag

Now the change has been added to latest (stable version) so we wanted to switch back. But if change unstable tag to latest, the site breaks following some UI error messages as shown in screenshots below.

We are unable to see any list contents if we click on any list items. Is there anything else that needs to be taken care of before switching or am I doing this wrong way. Adding some referenc epoint logs. Steps :

• when the container is started
• few moments later
• when we click any list
• log error after we click any list item in UI

Observations :

1. This affects overview, upcoming, and any list item, either not loading or loads with same error as above (internal server error) in UI.
2. However the projects list is still loading. I believe this is only occuring when trying to fetch list items.
3. We can see in error log that same error is repeating but with different code as shown in following images.
   

Note: We are using microsoft todo integration which might be an extra step than standard installation. Ref : #238 This was fixed and was working. So hopefully this does not add overhead to look for error but including this to be on same page for setup.

• In logs screenshot we have just removed IP address information. Rest is as is. Hope this info helps. Thanks in advance.

Vikunja Version

v0.23.0+577-fd126fa234

Browser and version

Firefox 125.0.2 (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Viknuja Version :

Browser Version :

Changes Made :

Errors:

• 
• 
• 
• 
• 
• 

[kolaente]

When did you switch? From 0.23.0 to the version you listed?

[inuonly]

today at the time of writing this issue itself. around 2 hours ago. I took the screenshots by actually changing from unstable to latest in docker compose file then taking screeenshots and then back to unstable as in current state latest tag was unusable for my instance as of now.

[kolaente]

Downgrading is generally not supported. You can only switch to the next stable release or newer unstable builds once you've switched to unstable. To switch from your unstable installation to a stable version you need to wait for the next release (0.24) and then upgrade from unstable to that.

You have two options now:

1. Roll back to 0.23.0 and restore from the last backup you have on that version
2. Stay on unstable until 0.24.0 is released.

If you only want to check things with an unstable build, you should either make the switch generally or make a backup, upgrade to unstable, check whatever you want to check, then go back to the last release and restore from backup.