PHP Warnings

  • Resolved Malae

    (@malae)


    4 months, 3 weeks ago

    Hello Kevin,
    Using WordPress 6.8 with PHP 8.3, I have the following PHP warnings flooding the wp_debug log file:

    PHP Warning: Undefined array key "fp_bluetooth_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    PHP Warning: Undefined array key "fp_captured-surface-control_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    PHP Warning: Undefined array key "fp_compute-pressure_src_domain" in /home/u730660366/domains/fwhr.transapex.com/public_html/wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    Undefined array key "fp_cross-origin-isolated_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    Undefined array key "fp_deferred-fetch_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    Undefined array key "fp_deferred-fetch-minimal_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    Undefined array key "fp_otp-credentials_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    Undefined array key "fp_storage-access_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791
    Undefined array key "fp_window-management_src_domain" in /wp-content/plugins/security-header-generator/work/inc/kcp-cspgen-headers.php on line 791

    I would appreciate your taking a look at this as I am hoping to upgrade to PHP 8.4.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Malae

    (@malae)

    4 months, 3 weeks ago

    Sorry WordPress is version 6.9.

    Plugin Author Kevin Pirnie

    (@kevp75)

    4 months, 3 weeks ago

    @malae

    I would appreciate your taking a look at this as I am hoping to upgrade to PHP 8.4.

    It is lower on the list to correct, since they are not system impeding in any way. They are… in fact… only warnings. You are safe to upgrade to 8.4

    Thread Starter Malae

    (@malae)

    4 months, 3 weeks ago

    Thank you for your prompt reply. I am aware that they are only warnings, but when I said flooding , that was an perhaps an understatement. The debug. file will grow to Megabytes size in a day and this requires the file to be downloaded to open. When I make changes to the site I activate the logging, but this issue makes it very difficult to use debugging and must resort to deactivating your plugin, which is not desirable.

    Plugin Author Kevin Pirnie

    (@kevp75)

    4 months, 3 weeks ago

    @malae

    I’m sorry Malae, but this is not something that is going to be prioritized. While I understand your position, the warnings; in no way shape or form; impede the functionality of your site nor the plugin.

    I can suggest to you to do the any of the following so you will not see the Warnings anymore.

    • Turn off WP-DEBUG by adding the following to your wp-config.php: define( 'WP_DEBUG', false );
    • Configure those items in the admin.php?page=wpsh_settings#tab=permissions-policy-headers page of the plugin.
    • Deactivate the plugin and keep an eye on the changelogs to see if they have been fixed in future updates.
    • This reply was modified 4 months, 3 weeks ago by Kevin Pirnie.
    Thread Starter Malae

    (@malae)

    4 months, 2 weeks ago

    @kevp75

    Thank you for the reply.

    If I want to debug other issues the the wp_debug must be set to true, but with the volume of PHP warnings from the Security Header Generator this is not practical.

    The simplest solution is to deactivate the plugin until the PHP is fixed. In the meantime, I will add CSP headers to the .htaccess file, which have worked well in the past.

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

You must be logged in to reply to this topic.