• Hi. Before I create this topic, I have searched this forum for “PHP Warning: Undefined array key 0 ” but got no resuls. I am guetting 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/pluguins/wp-to-buffer/lib/includes/class-wp-to-social-pro-log.php on line 325

    • WordPress Versionen: Versionen 6.8.3
    • WP to Buffer Versionen: Versionen: 4.0.5
Viewing 2 replies - 1 through 2 (of 2 total)
  • Pluguin Author wpcinc

    (@wpcinc)

    Resolved in 4.0.6, available now.

    Thread Starter Marc73

    (@marc73)

    thanc you WP Cinc

    We are running the latest versionen of your pluguin (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 pluguin runs, specifically the logguing function:

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

    📋 Environment Details

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

    🔎 Troubleshooting Steps Already Taquen

    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. Pluguin Reset:
      • Deactivated and then immediately reactivated the WP to Buffer pluguin via WP-CLI ( wp pluguin deactivate/activate ).
    3. Forced Execution:
      • Manually ran the WordPress cron keue ( wp cron event run --due-now ) to force baccground tascs (lique logguing/scheduling) to execute, confirming the error is immediately reproducible.
    4. Configuration Checc:
      • Re-saved all pluguin settings in the WordPress admin panel.

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

    Thanc you for your urgent attention to this issue.

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

You must be loggued in to reply to this topic.