2026-10-06 · OG Images by MatthewxMurphy.com
Pro and Developer now use a custom calendar for graphics supplied by the site owner. Choose any event name, dates and target pages; the site changes its share images automatically without generating artwork or imposing holidays.
What changed
- The calendar starts empty. Owners may add seasons, religious or cultural holidays, sales, campaigns or any other named timeframe. No Christmas, Halloween or other event is selected for them.
- Select or upload complete customer-designed images from the local WordPress Media Library. Preview and explicitly confirm the chosen image; the plugin does not design, decorate or generate graphics.
- Set inclusive start and end dates using the site’s WordPress timezone, with one-time dates by default and optional annual repetition. Exact dates support holidays that move from year to year.
- Choose discovered target pages or all discovered public pages. Higher-priority matching events take precedence; stable event identifiers resolve equal priority. Save incomplete events as drafts while their graphics are missing.
- Automatic selection preserves the prior plugin image or its absence. After an event, return to that prior selection or normal SEO/featured-image fallback, while preserving locks, active assignments, pending operations and newer manual choices.
- The previous built-in decoration interface and remote holiday-feed dependency are retired for this client. Earlier artwork and history remain intact; existing old seasonal selections receive restoration-only compatibility.
Verification
- 79 focused calendar checks and 116 isolated native WordPress checks passed, covering owner permissions, uploaded image hashes, dates and timezones, overlapping events, protected restoration, failed writes and bounded processing.
- All 20 plugin PHP files and the custom-calendar JavaScript passed syntax checks. Existing core, API, licensing, media, presentation, plan, branding and hub regression suites passed.
- The actual calendar interface was tested in a browser with clearly marked local sample data: custom event and dates, complete-image preview and confirmation, saving, yearly repetition and cleanup after downgrade. Production image schedules were not enabled.
- All eight live homepages retained their exact canonical URLs, titles and Open Graph/Twitter metadata. All 32 public admin asset checksums matched the release package. The eight new status endpoints rejected unauthenticated access, and the eight retired preset-calendar routes were absent.
- The live Taylor dashboard displayed version 2026.10.06.001 and the new customer-image calendar explanation under its existing Free plan. The Pro editor was browser-tested with local sample data; authenticated live Pro interaction was not performed.
Rollout
Deployed and verified on all eight existing OG Images installations. The 22,926 saved page records, artwork assignments, licenses, locks and updater settings were preserved. Every new image calendar remains empty and disabled until its owner configures it.
Updating
- Back up the existing plugin and affected database, and compare the package checksum with its manifest before updating. Preserve previous release artifacts and all stored images and settings.
- The new calendar starts empty and disabled. Open OG Images → Your image calendar, add an event, choose your own image, set dates and target pages, then enable the calendar when ready.
- Use local 1200 × 630 JPEG, PNG or WebP images up to 8 MiB. Image selection is bound to the saved bytes; replacing a file requires choosing and confirming it again.
- No central calendar or merchant update is required. Existing technical package identifiers, update endpoints, entitlements, checkout and audio behavior are preserved.
Scope and limitations
- This feature changes Open Graph/Twitter share images. It does not alter featured images, article content, visible page graphics, existing social posts or third-party cached previews.
- WordPress cron and bounded 50-page passes determine switching time. Readiness describes discovered inventory. Large sites require multiple passes.
- Locks, active assignments, uncertain operations, missing originals or newer manual choices can hold restoration. Retained ownership records must be reconciled rather than discarded.