Issue: Entries not showing in 1.23.0 / Blank Dashboard - Items still viewable when entering the Asset Tag directly (Only affects German language user setting)

[IT-KT]

After the latest Update to 1.23.0 (Snipe-IT 8.8.0) we can not "browse" anything.

Clicking on Items, Licenses, Users, etc. just shows a blank page, but it still shows the number of items in each category:

Entering an asset tag in the top right search opens the asset normally but viewing its history or any other tab also opens blank:

Restarting the app did not help.

[james]

Hello @it-kt

I found the issue. This only affects the German language users of @snipe-it
It has already been reported and fixed upstream https://github.com/grokability/snipe-it/issues/19736

The quick fix is to change the language in your profile $sub.domain.tld/account/profile to English.
We will have to wait for an 8.8.1 release that includes the fix for the German language.

[james]

Hello @it-kt and welcome to the Cloudron forum

Thanks for reporting, I will look into it.

[IT-KT]

@james , thanks!

We just restored a backup from yesterday to 1.22.2 and that works fine - so no pressing issue for us at the moment.

[james]

Hello @it-kt
Can you please provide the app log to me with https://paste.cloudron.io/?

Edit:
@it-kt provided the log file in a private message

[james]

Hello @it-kt

I found the issue. This only affects the German language users of @snipe-it
It has already been reported and fixed upstream https://github.com/grokability/snipe-it/issues/19736

The quick fix is to change the language in your profile $sub.domain.tld/account/profile to English.
We will have to wait for an 8.8.1 release that includes the fix for the German language.

[IT-KT]

@james , thanks for investigating this so quickly and finding the issue! Can confirm - works with English language.

My lesson learnt today: also search the closed issues on github

[james]

Hello @IT-KT

@IT-KT said:

My lesson learnt today: also search the closed issues on github

I always remove the state:open filter in the GitHub issue search.
That did cost me many hours to only figure out later there already was an issue, and it has already been fixed but not released yet.