mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-12 23:31:02 +00:00
Maurice
247d5fc519
An installation now asks for its TREK services key a few minutes after it starts, and the daily check registers a missing key as well as renewing a due one. Until now nothing happened before someone searched for a place or opened the admin settings, so "Share place details" stayed unavailable on a fresh or updated instance. When an admin agrees to share place details, what users typed into places since TREK 5.1.0 goes out too, not only what they type from then on. The origin of every field is recorded since 5.1.0 whatever the decision, so a catch-up walks those places page by page before each send run: only values that are still the ones a user typed, only for fields switched on, only for places the service can key, and only while the queue holds fewer than 200 values. It goes on where it stopped after a restart, never replaces a newer value a save queued, and ends on switching off, declining or withdrawing everything. A field switched on later catches up as well, under an agreement given with the new prompt sentence that says so; an agreement from 5.1.0 does not. Queuing moves into PlaceContribQueue so a save and the catch-up take the same path.