• Resolved Marc73

    (@marc73)


    Hi. Before I create this topic, I have searched this forum for “PHP Warning: Undefined array key 0 ” but got no results. I am getting this error in my logs.

    [15-Nov-2025 08:43:58 UTC] PHP Warning: Undefined array key 0 in /usr/www/users/mydomain/wp-content/plugins/wp-to-buffer/lib/includes/class-wp-to-social-pro-log.php on line 325

    • WordPress Version: Version 6.8.3
    • WP to Buffer Version: Version: 4.0.5
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author wpzinc

    (@wpzinc)

    Resolved in 4.0.6, available now.

    Thread Starter Marc73

    (@marc73)

    thank you WP Zinc

    We are running the latest version of your plugin (4.0.6) and are experiencing a persistent PHP Warning that is flooding our error logs. This warning appears to be the bug you intended to fix in the 4.0.6 release.

    The following warning is generated repeatedly in the PHP error log whenever the plugin runs, specifically the logging function:

    PHP Warning: Undefined array key 0 in /usr/www/users/mydomain/wp-content/plugins/wp-to-buffer/lib/includes/class-wp-to-social-pro-log.php on line 327

    📋 Environment Details

    • Plugin Version: 4.0.6 (Latest)
    • PHP Version: 8.4
    • WordPress Version: 6.8.3
    • Caching: Redis Object Cache is active.

    🔎 Troubleshooting Steps Already Taken

    To rule out any environmental or data corruption issues, we have performed the following comprehensive steps, and the warning still persists:

    1. Cache/Transient Cleanup:
      • Executed wp cache flush multiple times.
      • Executed wp transient delete --all.
    2. Plugin Reset:
      • Deactivated and then immediately reactivated the WP to Buffer plugin via WP-CLI (wp plugin deactivate/activate).
    3. Forced Execution:
      • Manually ran the WordPress cron queue (wp cron event run --due-now) to force background tasks (like logging/scheduling) to execute, confirming the error is immediately reproducible.
    4. Configuration Check:
      • Re-saved all plugin settings in the WordPress admin panel.

    Since the error persists after these steps, we believe this is an unresolved bug in the plugin’s code logic (Line 327) that may be triggered by specific data in our installation. Please investigate this line in version 4.0.6 for an unhandled array return or empty variable access.

    Thank you for your urgent attention to this issue.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.