root
b6df4dbb92
MLS plugin fixes from this session: - Fix silent insert failures: location column NOT NULL was rejecting wpdb->insert calls, causing ~18k new properties since Dec 2025 to be lost. Inserts now build raw SQL with ST_PointFromText so the spatial column is populated atomically. - Auto-refresh expired media URLs in MLS_Media_Handler::fetch_and_cache(), guarded by a property-level GET_LOCK so concurrent fetches share one API refresh. - Normalize WP_Error to null in mls_get_property_image() so callers can rely on the documented string|null contract. - Support comma-separated property_type filters in MLS_Query and MLS_Cluster so the homepage "View All Commercial" link (?property_type=Commercial+Sale,Land,Farm) actually filters correctly. - Incremental sync now looks back 10 minutes past the latest modification timestamp as a safety margin against missed records. - Smart sync exits silently (info-level, not warning) when a full sync is in progress. Operational: - New cron: weekly full sync Sundays at 3 AM (/usr/local/bin/mls-full-sync). - New cron: hourly 2GB cap on mls-thumbnails/ and cache/transformed-images/ (/usr/local/bin/mls-image-cache-cap). - Logrotate config for wp-content/debug.log (2-day retention, daily rotation, delaycompress). Repo policy: - CLAUDE.md updated with explicit "commit everything except build artifacts" policy. - .gitignore: untrack runtime image caches and debug.log rotations. Other modifications in this snapshot are pre-existing in-flight theme/plugin/db_content_updates work. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.6 KiB
Executable File
1.6 KiB
Executable File
Database Content Updates
This directory contains documentation for all database content changes made in development that need to be applied to production.
When to Create a Document
Create a document here whenever you make changes to:
- WordPress options (
wp_optionstable) - ACF field values (Theme Options, page fields, etc.)
- Posts, pages, or custom post type content
- Menus and menu items
- Taxonomy terms
- User meta or other wp_usermeta changes
Document Format
Filename: YYYY-MM-DD_HH-MM_short-description.md
Example: 2026-01-04_19-30_add-properties-page.md
Required Sections:
# [Brief Title]
**Date**: YYYY-MM-DD HH:MM
**Author**: [Your name or "Claude"]
## Summary
One sentence describing what changed and why.
## Changes Made
### [Change 1 Title]
**Type**: [option | acf_field | post | menu | term | other]
**Table**: [wp_options | wp_postmeta | etc.]
**WP-CLI Command(s)**:
wp --allow-root [exact command here]
**Or SQL**:
[exact SQL here]
**Values Set**:
- field_name: "value"
- another_field: 123
### [Change 2 Title]
...
## Dependencies
- List any changes that must be applied first
- Or note "None" if standalone
## Verification
How to verify the change was applied correctly:
- Check URL: /some-page/
- Verify in admin: Settings > Theme Options > Tab Name
Important Notes
- Be EXACT - copy/paste actual commands and values
- Include post IDs, option names, field keys - no ambiguity
- If order matters, number the steps
- Test your commands before documenting them
- Production team will execute these verbatim