• Deprecated: ITSEC_Settings::__construct(): Implicitly marking parameter $config as nullable is deprecated, the explicit nullable type must be used instead in /home/xxx/public_html/blog/wp-content/plugins/better-wp-security/core/lib/settings.php on line 21

    Deprecated: ITSEC_Settings::is_conditional_setting_active(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/xxx/public_html/blog/wp-content/plugins/better-wp-security/core/lib/settings.php on line 162

    Deprecated: ITSEC_Modules::load_module_file(): Implicitly marking parameter $process as nullable is deprecated, the explicit nullable type must be used instead in /home/xxx/public_html/blog/wp-content/plugins/better-wp-security/core/modules.php on line 730

    Deprecated: ITSEC_Lib::equal_sets(): Implicitly marking parameter $cmp as nullable is deprecated, the explicit nullable type must be used instead in /home/xxx/public_html/blog/wp-content/plugins/better-wp-security/core/lib.php on line 2282

    Deprecated: Method SplObjectStorage::attach() is deprecated since 8.5, use method SplObjectStorage::offsetSet() instead in /home/xxx/public_html/blog/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 180

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Pawel [SolidWP Support]

    (@solidwppawel)

    Hi @bigbatsbutt,

    Thank you for the detailed report. I can confirm that all five deprecation notices you’re seeing are present in the current version of Solid Security.

    The notices are caused by implicitly nullable parameter types, which PHP 8.4 started flagging as deprecated.

    These are deprecation notices only and should not affect the plugin’s functionality. That said, they can be noisy, especially if your error reporting includes E_DEPRECATED.

    Our development team is aware of the PHP 8.4+ compatibility gaps. Until an updated version is released with these fixes, the most reliable workaround is to use PHP 8.3, which is fully compatible with the current version.

    I’ll flag your report internally to help prioritize these fixes. Thank you for taking the time to document each notice — it’s very helpful.

    Kind regards,
    Paweł

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

You must be logged in to reply to this topic.