Skip to content

v1.4.1 — Image hash storage fix

Choose a tag to compare

@rollacode rollacode released this 31 Mar 18:14
· 7 commits to main since this release

Fix

  • Backend: Image hashes were not stored in the database because the upsert used LWW (last-writer-wins) condition which required a newer client_modified timestamp. Changed to simple COALESCE — fills empty hash without timestamp check.
  • After updating backend, do a Full Resync from one client to populate all hashes.

Update backend required. Plugin unchanged from v1.4.0.