PHP Warning: Undefined array key

  • Resolved Jarko Piironen

    (@ipajen)


    5 months ago

    After updating to latest Version 2.26.10 following PHP warnings are shown in debug logs.

    PHP Warning:  Undefined array key "continent_code" in /public_html/blog/wp-content/plugins/limit-login-attempts-reloaded/core/Ajax.php on line 451

    PHP Warning:  Undefined array key "offset" in /public_html/blog/wp-content/plugins/limit-login-attempts-reloaded/core/Ajax.php on line 677

    === Environment
    – WordPress: 6.6-beta3
    – PHP: 8.3.8
    – Server: LiteSpeed
    – Database: mysqli (Server: 10.6.18-MariaDB / Client: mysqlnd 8.3.8)
    – Browser: Edge 126.0.0.0 (Windows 10/11)
    – Theme: Twenty Twenty-Four 1.1
    – MU-Plugins:
      * block-automation-by-installatron.php
      * Health Check Troubleshooting Mode 1.9.0
    – Plugins:
      * Core Rollback 1.3.5
      * Enable jQuery Migrate Helper 1.4.0
      * Health Check & Troubleshooting 1.7.0
      * Limit Login Attempts Reloaded 2.26.10
      * Plugin Check (PCP) 1.0.1
      * Plugin Compatibility Checker 3.0.1
      * Query Monitor 3.16.3
      * Stop User Enumeration 1.6
      * WordPress Beta Tester 3.5.5
      * WP Hooks Finder 1.3.1
      * WP SMS 6.9.1
      * WPVulnerability 3.2.0

    Also shown at: Report – Limit Login Attempts Reloaded 2.26.10 – PluginTests.com

Viewing 3 replies - 1 through 3 (of 3 total)
  • martje65

    (@martje65)

    We have the same PHP Warning in your log files.

    PHP Warning: Undefined array key “continent_code” in /wp-content/plugins/limit-login-attempts-reloaded/core/Ajax.php on line 451\n, referer: wp-admin/admin.php?page=limit-login-attempts&tab=dashboard
    PHP Warning: Undefined array key “offset” in /wp-content/plugins/limit-login-attempts-reloaded/core/Ajax.php on line 677\n, referer: wp-admin/admin.php?page=limit-login-attempts&tab=dashboard

    PHP: 8.2.18,
    WordPress: 6.5.4
    Woocommerce: 9.0.1
    Limit Login Attempts Reloaded: 2.26.10

    Plugin Author WPChef

    (@wpchefgadget)

    We’ve deployed a fix for this in the new 2.26.11. Please install the latest version.

    martje65

    (@martje65)

    @wpchefgadget Everything works fine and the warning is gone.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.