Closed CHBMB closed 5 years ago
In short, looks like something broke between v2.3.0 and v2.4.0. Looking at the grocy issues page, nothing seems to have been reported. v2.4.0 was only released a couple of days ago though. Scanning the changelog the only thing that caught my eye as potentially an issue is this:
Internal improvement: Localizations are now handled via gettext, both on server and client side
Mainly to properly handle languages with more than 2 plural forms
This involved some string changes which results in a needed (re)translation of about 20 strings (excluding demo data)
Also applies to quantity units, n-plural forms can be entered on the quantity unit edit page
It's not required to install the PHP gettext extension, on both, server and client, managed implementations of gettext are used (oscarotero/Gettext & oscarotero/gettext-translator)
apk add php7-gettext
fwiw didn't resolve the issue.
Nor did
apk add composer
composer require gettext/gettext
Unraid
Seems a few people are having this issue, and I was able to reproduce it locally on
latest
&linuxserver/grocy:v2.4.0-ls17
Rolled back to
linuxserver/grocy:v2.3.0-ls16
and a fresh pull of that was working.To further complicate things, using the
/config
folder fromv2.4.0-ls17
with the image fromv2.3.0-ls16
also doesn't work with a blank webui.Using the
/config
folder fromv2.3.0-ls16
with the image fromv2.4.0-ls17
results in the webui coming up withSlim Application Error
and the following being displayed on the browser page.