• Resolved Jeremy Nusser

    (@nusserstudioscom)


    I get these errors when I ‘m debugging my local site. The plugin will retain settings and works fine. I just get these errors right after pressing the update button. Not a big deal, but as PHP7 is adopted by more hosts and users, you may want to correct it.

    ( ! ) Notice: options.php was called with an argument that is deprecated since version 2.7! The aj_enabled setting is unregistered. Unregistered settings are deprecated. See https://codex.wordpress.org/Settings_API in /srv/www/example.com/current/web/wp/wp-includes/functions.php on line 3737
    Call Stack
    # Time Memory Function Location
    1 0.0008 421664 {main}( ) …/options.php:0
    2 0.3944 26545144 _deprecated_argument( ) …/options.php:202
    3 0.3945 26545464 trigger_error ( ) …/functions.php:3737

    ( ! ) Notice: options.php was called with an argument that is deprecated since version 2.7! The aj_method setting is unregistered. Unregistered settings are deprecated. See https://codex.wordpress.org/Settings_API in /srv/www/example.com/current/web/wp/wp-includes/functions.php on line 3737
    Call Stack
    # Time Memory Function Location
    1 0.0008 421664 {main}( ) …/options.php:0
    2 0.3945 26545288 _deprecated_argument( ) …/options.php:202
    3 0.3945 26545608 trigger_error ( ) …/functions.php:3737

    ( ! ) Notice: options.php was called with an argument that is deprecated since version 2.7! The autoptimize_enabled setting is unregistered. Unregistered settings are deprecated. See https://codex.wordpress.org/Settings_API in /srv/www/example.com/current/web/wp/wp-includes/functions.php on line 3737
    Call Stack
    # Time Memory Function Location
    1 0.0008 421664 {main}( ) …/options.php:0
    2 0.3946 26545288 _deprecated_argument( ) …/options.php:202
    3 0.3946 26545608 trigger_error ( ) …/functions.php:3737

    ( ! ) Notice: options.php was called with an argument that is deprecated since version 2.7! The aj_exclusions setting is unregistered. Unregistered settings are deprecated. See https://codex.wordpress.org/Settings_API in /srv/www/example.com/current/web/wp/wp-includes/functions.php on line 3737
    Call Stack
    # Time Memory Function Location
    1 0.0008 421664 {main}( ) …/options.php:0
    2 0.3948 26545288 _deprecated_argument( ) …/options.php:202
    3 0.3948 26545608 trigger_error ( ) …/functions.php:3737

    ( ! ) Warning: Cannot modify header information – headers already sent by (output started at /srv/www/example.com/current/web/wp/wp-includes/functions.php:3737) in /srv/www/example.com/current/web/wp/wp-includes/pluggable.php on line 1228
    Call Stack
    # Time Memory Function Location
    1 0.0008 421664 {main}( ) …/options.php:0
    2 0.3968 26531888 wp_redirect( ) …/options.php:239
    3 0.3969 26534640 header ( ) …/pluggable.php:1228

    https://wordpress.org/plugins/async-javascript/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Frank Goossens

    (@futtta)

    So I first wrote;

    I’ll take the autoptimize one 😉

    except this probably is a setting in async javascript, so I can’t fix that, can I (thought for a second this was an AO setting).

    sorry for the noise 😉

    frank

    Thread Starter Jeremy Nusser

    (@nusserstudioscom)

    No worries, and you’re right Frank, I just have AO installed as well, but this is a setting in AJ. Lines 81-84. This isn’t anything critical, just wanted to give David a heads up.

    $aj_enabled = (get_option(‘aj_enabled’) == 1) ? array(true,’checked’,”) : array(false,”,’style=”display:none;”‘);
    $aj_method = (get_option(‘aj_method’) != ‘async’) ? ‘defer’ : ‘async’;
    $aj_exclusions = get_option(‘aj_exclusions’);
    $autoptimize_enabled = (get_option(‘autoptimize_enabled’) == 1) ? ‘checked’ : ”;

    Plugin Author Frank Goossens

    (@futtta)

    The reason for my confusion stems from the fact that the settings name is autoptimize_enabled, which looks like an AO option. It would be better to prepend that name with aj_ as for the other settings, so it would be aj_autoptimize_enabled. Would be great if the developer could take care of that as well 🙂

    Plugin Author David Clough

    (@cloughit)

    Hi Jeremy / Frank,

    Thanks for the heads up. Whilst I haven’t got a PHP7 environment to test in the issue is clear and I have released an update to (hopefully) combat the issue you are seeing. It would be greatly appreciated if you could let me know if the latest version (1.16.03.11) has removed the error messages you are seeing.

    Frank, I have also taken on board the suggestion of changing the option name for autoptimize_enabled.

    Thread Starter Jeremy Nusser

    (@nusserstudioscom)

    No problem David, it was indeed Version 1.16.02.18. Still seeing the issue however. Version 1.16.03.11

    Plugin Author David Clough

    (@cloughit)

    Bugger… but then again it is always good to learn something new which this experience has provided!

    Please update to the latest version 1.2016.03.12 and (hopefully) you will find the issue resolved.

    Plugin Author Frank Goossens

    (@futtta)

    Frank, I have also taken on board the suggestion of changing the option name for autoptimize_enabled.

    Confirmed resolved, thanks David!

    Small suggestion; after updating $aj_autoptimize_enabled with the value of $autoptimize_enabled and updating the ‘aj_autoptimize_enabled’ option with that value, you could also delete the ‘autoptimize_enabled’ option, to clean things up nicely? 🙂

    frank

    Thread Starter Jeremy Nusser

    (@nusserstudioscom)

    That did it! Thanks David!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘PHP7 Debugging Error’ is closed to new replies.