• Resolved nochi106y

    (@nochi106y)


    After updating my WordPress installation to version 6.7.1 and updating the iThemes Security plugin, I encountered the following error:

    Notice: Trying to access array offset on value of type null in /better-wp-security/core/modules/security-check-pro/class-itsec-security-check-pro.php on line 52
    The error seems to originate from the “Security Check Pro” module in the plugin. It occurs on line 52 of the class-itsec-security-check-pro.php file, specifically when attempting to access the name offset of the $ip_header variable.

    I did not experience this issue before updating WordPress and the plugin. Could you please provide guidance on how to resolve this error in a way that avoids directly modifying the plugin files? I would like to prevent similar errors from reoccurring during future updates.

    If there is an existing question and solution addressing the same issue, a link to that would be greatly appreciated.

    Thank you for your assistance.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi @nochi106y,

    What is the PHP version being used?

    And did you update the PHP version recently?

    +++ To prevent any confusion, I’m not SolidWP +++

    Thread Starter nochi106y

    (@nochi106y)

    Hi @nlpro ,

    We are using PHP 7.4.33.
    The PHP version has not been updated.

    Thread Starter nochi106y

    (@nochi106y)

    I resolved the issue by deleting the plugin file and re-uploading it.

    Hi @nochi106y,

    Excellent. Re-install of the plugin was definately an option in the back of my mind.

    Nevertheless I think this topic uncovered a potential PHP backward compatibility issue in the plugin code. So even though the topic is resolved I’ll try and draw SolidWPs attention to it ??

    @shanedelierrr

    IMHO this is an a potential “Array-style access of non-arrays” PHP backward compatibility issue in the Security Check Pro module code of the SolSec plugin.

    Plugin Support chandelierrr

    (@shanedelierrr)

    @nochi106y glad to hear it’s resolved! Excellent troubleshooting!

    And thanks for the heads-up @nlpro! I’ve reported this to our team for review and resolution.

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