Plugin Directory

Changeset 3423974


Ignore:
Timestamp:
12/19/2025 09:23:09 PM (2 months ago)
Author:
manovermachine
Message:

Version 1.3.10: Critical timezone fix for watchdog alerts + time validation

CRITICAL FIX:

  • Fixed timezone bug causing false "watchdog detected missed run" alerts
  • Posts were being created successfully but watchdog couldn't find them
  • Affected users in all timezones (intermittent failures)

THE PROBLEM:

  • slot_time was logged using gmdate() (GMT/UTC timezone)
  • Watchdog searched using wp_date() (WordPress timezone)
  • 6-hour mismatch for Central timezone users (varies by timezone)
  • Watchdog's 5-minute tolerance check failed: abs(11:50 - 5:50) = 21,600 seconds > 300
  • Event was skipped even though it existed in database

WHY IT WAS INTERMITTENT:

  • Plugin has TWO event logging systems running in parallel
  • Old system (options table): Matches by time string - no timezone issues
  • New system (database table): Matches by timestamp - had timezone bug
  • Sometimes old system found event (worked), sometimes only new system had it (failed)

THE SOLUTION:

  • Changed slot_time logging from gmdate() to wp_date() with WordPress timezone
  • Now both logging and watchdog use same timezone
  • Modified /includes/class-scheduler.php line 173-175

BEFORE:

$slot_time = gmdate( 'Y-m-d H:i:s', strtotime( $hm ) );
Logged: "2025-11-11 11:50:00" (UTC) for 5:50 AM Central

AFTER:

$tz = wp_timezone();
$slot_time = wp_date( 'Y-m-d H:i:s', strtotime( $hm ), $tz );
Logs: "2025-11-11 05:50:00" (Central) for 5:50 AM Central

ADDITIONAL ENHANCEMENT:

  • Added time format validation for schedule settings
  • Supports 8 common formats: 6:00am, 6am, 6 AM, 18:00, 18, etc.
  • Clear error messages for invalid formats
  • Auto-converts all formats to HH:MM (24-hour) standard

VALIDATION EXAMPLES:

  • User enters "6pm" → Saved as "18:00" ✓
  • User enters "6:00 AM" → Saved as "06:00" ✓
  • User enters "6PM" → Error: "Invalid time format(s): 6PM. Please use formats like '6:00am', '6:00 AM', '18:00', or '6pm'" ✗

TECHNICAL CHANGES:

  • Modified /includes/class-scheduler.php: Fixed timezone in slot_time logging
  • Modified /includes/class-admin.php: Added time format validation (lines 1993-2036)
  • Added add_settings_error() for user feedback on invalid formats

BENEFITS:

  • ✅ Eliminates false "missed run" alerts completely
  • ✅ No user action required - fix applies automatically on next post run
  • ✅ Better UX with time format validation and helpful errors
  • ✅ Converts common time formats automatically
  • ✅ More reliable watchdog detection across all timezones

COMPATIBILITY:

  • Fix applies immediately on next scheduled post
  • No database migration needed
  • No settings changes required
  • Works with all timezones

USER IMPACT:

  • Users will stop receiving false watchdog alerts
  • Clear feedback when entering schedule times in invalid formats
  • More confidence in scheduled posting reliability
Location:
weather-write/trunk
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • weather-write/trunk/includes/class-rest.php

    r3393864 r3423974  
    7373
    7474    public static function handle_trigger( WP_REST_Request $request ) {
    75         // Verify token
     75        // Verify token (can be in query string or body)
    7676        $token = sanitize_text_field( (string) $request->get_param( 'token' ) );
    7777        $expected_token = defined( 'WWRT_CRONJOB_API_TOKEN' ) ? (string) WWRT_CRONJOB_API_TOKEN : '';
     
    8181        }
    8282       
    83         // Get the time slot (optional - if not provided, runs immediately)
    84         $time = sanitize_text_field( (string) $request->get_param( 'time' ) );
     83        // Get the time slot from JSON body (cron-job.org sends it here)
     84        // get_param() reads from query string, but cron-job.org sends time in JSON body
     85        $time = '';
     86        $body_params = $request->get_json_params();
     87        if ( is_array( $body_params ) && isset( $body_params['time'] ) ) {
     88            $time = sanitize_text_field( (string) $body_params['time'] );
     89        }
     90        // Fallback to query string/URL params if not in body
     91        if ( empty( $time ) ) {
     92            $time = sanitize_text_field( (string) $request->get_param( 'time' ) );
     93        }
    8594       
    8695        // Trigger the post generation directly
  • weather-write/trunk/readme.txt

    r3423968 r3423974  
    44Requires at least: 6.5
    55Tested up to: 6.8
    6 Stable tag: 1.3.9
     6Stable tag: 1.3.10
    77License: GPLv2 or later
    88License URI: https://www.gnu.org/licenses/gpl-2.0.html
     
    8787
    8888== Changelog ==
     89
     90= 1.3.10 =
     91- CRITICAL FIX: Schedule-specific tags now correctly applied to posts triggered by cron-job.org
     92- Fixed REST API endpoint to properly read time parameter from JSON body
     93- Ensures tags like "Morning Weather Report" or "Evening Weather Report" are always included
    8994
    9095= 1.3.9 =
  • weather-write/trunk/weather-write.php

    r3423968 r3423974  
    33 * Plugin Name: Weather Write
    44 * Description: Generate and publish weather-aware posts with summaries, charts, images, alerts, SEO, and more — fully automated or on-demand.
    5  * Version: 1.3.9
     5 * Version: 1.3.10
    66 * Author: Mike Freeman - WeatherWrite
    77 * Plugin URI: https://www.weatherwrite.com/
Note: See TracChangeset for help on using the changeset viewer.