v4.1.33 — tag names are readable again, provider sign-in skips a pointless click, and source installs keep their database

Tag names are readable again, signing in with a provider skips a pointless click, and installing outside Docker finally keeps your database where the app reads it.

docker pull ghcr.io/new-usemame/calibre-web-nextgen:latest

What you'll notice

Tag names are readable again. The Tags page had been showing columns of … where the names should be — the grid was sized before the rename and delete buttons existed, so once those arrived they took their space out of the name itself. On a 152-tag library, names cut off went from 87% to 9% on desktop and 32% to 8% on a phone. Authors, Series and Publishers keep their layout and gain the same second line.

Signing in with your provider skips the extra click. If your server has standard login switched off and exactly one provider configured, the login page existed only to be clicked through. It now starts that provider straight away — and ?local=1 brings the plain page back, which is how an admin gets in when the provider itself is down. Cancelling at the provider used to bounce you straight back to it in a loop; that's fixed too. Contributed by @lduesing.

Spanish is complete; Traditional Chinese is much further along. Spanish now covers all 2,645 phrases, up from 1,378 — the most complete translation the project ships. Traditional Chinese went from 619 to 919. Both catalogues also had entries gettext had guessed and marked provisional, which are silently dropped when the catalogue is compiled, so they rendered in English while a translation sat in the file unused. 196 of those were confirmed or corrected in Spanish; a few had reversed the meaning of the original. Contributed by @HaruIjima-kun and @siuwai1999.

Your library folder stops collecting a stray metadata.db. Something during startup checked for a database at the top of your library folder, and the act of checking created an empty one there — the file that made versions 4.1.20 to 4.1.31 refuse to start for some people. It's no longer created at all, and two things that had been reading it instead of your real library now find the right one: the KOReader checksum job, which had been failing with no such table: books on every restart, and your reading statistics, which had been reporting nothing.

The "help translate this" notice stops coming back. It was remembered by writing a file into the program folder, which gets replaced on every update. It now lives alongside your settings. Reported by @chloeroform.

If you install from source

This release is mostly for you. Running from a checkout, a distro package or a systemd unit used to write app.db, dirs.json and your CWA settings into a /config folder created at the top of the filesystem, while the app read from the folder you installed into — so you got a first-run setup screen and an empty library, with the real database sitting somewhere nothing opens.

All of them now resolve the same way. Alongside that:

• An install upgrading from one of those builds is told which database it found and given the setting that keeps it, instead of being handed an empty one. Nothing is moved or deleted for you, because only you know which copy you want.
• A failure to open the settings database now says which path it tried and exits non-zero. It used to exit zero, so an import could die partway through while the supervisor recorded a clean run.
• First run no longer prints chown: invalid user: 'abc:abc' and a traceback for something that wasn't an error.
• The version no longer reports one release behind, so the update check stops offering an update you already have.

Docker installs set these paths explicitly and are byte-for-byte unaffected. Reported and driven by @Thovi98, who packages Calibre-Web NextGen for YunoHost, with cps/ cleanup from @chloeroform.

Also in this release

• A third-party KOReader sync client is no longer left guessing why a book looks unsynced — the server now says when it's holding back a percentage-only position and how to ask for it, and the sync protocol documentation covers both formats. Reported by @sroebert, who hit this building Crossink.
• The log no longer opens with a rate-limiter storage warning on every startup. Nothing about rate limiting changes. Reported by @chloeroform.

Full detail in CHANGELOG.md.

Something still broken?

Open an issue at new-usemame/Calibre-Web-NextGen/issues or say hello on Discord. Both get read.