Sergei Poljanski
6f37e537ca
The "updated" date and the sitemap lastmod came from max(created_at), so editing a datacenter, fixing an incident title or deleting an incident left them stale. Google stops trusting lastmod once it is seen to be wrong. Migration 014 adds updated_at (backfilled from created_at). Saves set it, renumbering bumps only the rows whose position actually moved, and deleting an incident bumps its datacenter. The admin delete now goes through the model so the hook runs. The sitemap gives lastmod as a full timestamp and drops changefreq, which Google ignores. Assisted-by: Claude:opus-5 |
||
|---|---|---|
| .. | ||
| 001_invoices.rb | ||
| 002_invoice_ltc.rb | ||
| 003_invoice_crypto.rb | ||
| 004_bingo.rb | ||
| 005_bingo_photo_variants.rb | ||
| 006_bingo_mw_type.rb | ||
| 007_users.rb | ||
| 008_user_tokens_audit.rb | ||
| 009_invoice_cancel_hide.rb | ||
| 010_payout_addresses.rb | ||
| 011_users_choose_username.rb | ||
| 012_payout_addresses_rework.rb | ||
| 013_bingo_photo_og.rb | ||
| 014_bingo_updated_at.rb | ||