Repository navigation
v1.4.1 — Image hash storage fix
Fix
- Backend: Image hashes were not stored in the database because the upsert used LWW (last-writer-wins) condition which required a newer
client_modifiedtimestamp. 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.