github Casvt/Kapowarr V1.0.0-beta-3

latest releases: V1.0.0, V1.0.0-beta-4
12 months ago

What's Changed

Added

  • Added support for one-shots
  • Added support for hard covers
  • Kapowarr avoids all download links from shorte.st
  • Improved searching by adding extra search terms
  • Added logo in UI and docs
  • Downloads aren't added to the queue if they're already in it
  • Added support for PWA (adding the web-UI to your home screen as if it was an app) (#28)
  • Added check for CV token to see if it's valid and working when it's entered in the settings

Changed

  • Fixed/Improved some things regarding downloading from GC (among other things, #82)
  • Fixed Kapowarr fetching new issues for volumes (see note below)
  • Improved matching files when scanning for them
  • Improved matching search results that contained the 'and' word
  • Fixed deleting a volume when there is a download for it in the queue.
  • Show "Unknown" instead of "0TB" in the download queue for downloads with unknown size
  • Fixed Kapowarr adding download links to the blocklist when adding them on start-up
  • The backend has been refactored to: reduce the "database locked" error, fix various small bugs, make some things faster and get Kapowarr ready for more features.
  • Fixed the colour of links in the settings

Note

If you upgrade from beta-2 to beta-3, please run an "Update All" after upgrading. Kapowarr had a bug where it wouldn't fetch new issues of volumes. That is now fixed, which means that after upgrading, loads of new issues (depending on how many ongoing volumes you have) will appear for volumes, which will also be downloaded (if the volume and issue are monitored and a download is available). This bug has been in Kapowarr for quite some time, so there could be multiple new issues per ongoing volume (depending on how often the publisher releases new issues for the volume).

Technical explanation
ComicVine supplies a "date_last_updated" key which gives the date that the metadata was changed for the last time. Kapowarr made use of this value by only fetching all metadata for a volume if the value had changed since the last fetch. This way, metadata would only be fetched if it was changed compared to the local version.

It turns out that this value doesn't change when an issue is added to the volume (or removed/edited). So Kapowarr wouldn't update the metadata, even when new issues were released. Kapowarr would only update the metadata (and sync the issue list) when the metadata of the volume was changed, which doesn't happen very often. Because this is faulty behaviour, the system is removed and Kapowarr now always fetches all metadata. That means that suddenly all new issues that weren't fetched before, now will, and thus loads of new ones could appear.

Full Changelog: V1.0.0-beta-2...V1.0.0-beta-3

Don't miss a new Kapowarr release

NewReleases is sending notifications on new releases.