• Resolved davidblood

    (@davidblood)


    Hi,

    WP auto updated plugin to 3.2.6 and it broken the backend style rending. Unless I add define('CONCATENATE_SCRIPTS', false); to wp-config.php

    Main site also shows:

    Warning: Trying to access array offset on value of type null in /wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-front-end.php on line 1300
    Warning: Trying to access array offset on value of type null in /wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-front-end.php on line 1301

    Thoughts?

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • @davidblood Where do you see these warning messages, do you see it in error logs file or WordPress admin.

    As for the backend style rendering, we have tested the issue at our end but couldn’t reproduce, it works fine at our end.

    Have you performed a conflict test yet?

    Try deactivating all plugins except for WP-Optimize and see if it is resolved.

    If so, reactivate each plugin one at a time until you find the culprit. You can check for the issue between activating each plugin, so you can see which one is causing problems.

    Please let us know your findings.

    Thread Starter davidblood

    (@davidblood)

    Hi @bornforphp,

    I see these on the front page if debug is enabled via wp-config.php. It’s stopped now.

    Regarding the backend I fixed this by adding define('CONCATENATE_SCRIPTS', false); to wp-config.php – no clue what it does – I’m trusting stackoverflow with this one!

    I’m also seeing on Reddit that it might’ve been caused by Cloudflare’s recent outrage.

    Thanks.

    Thread Starter davidblood

    (@davidblood)

    Not sure if this helps..

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.0
    Active theme: Ocean (version 1.0.2)
    Current plugin: WP-Optimize - Clean, Compress, Cache (version 3.2.6)
    PHP version 7.4.30
    
    Error Details
    =============
    An error of type E_ERROR was caused in line 9 of the file /wp-content/plugins/wp-optimize/templates/minify/cached-file-log.php. Error message: Uncaught TypeError: property_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /wp-content/plugins/wp-optimize/templates/minify/cached-file-log.php:9
    Stack trace:
    #0 /wp-content/plugins/wp-optimize/templates/minify/cached-file-log.php(9): property_exists()
    #1 /wp-content/plugins/wp-optimize/wp-optimize.php(1223): include('/home/tlguzfgc/...')
    #2 /wp-content/plugins/wp-optimize/templates/minify/cached-file.php(15): WP_Optimize->include_template()
    #3 /wp-content/plugins/wp-optimize/wp-optimize.php(1223): include('/home/tlguzfgc/...')
    #4 /wp-content/plugins/wp-optimize/templates/minify/advanced-tab.php(31): WP_Optimize->include_template()
    #5 /wp-content/plugins/wp-optimize/wp-optimize.php(1223): include('/home/tlguzfgc/...')
    #6 /wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-admin.php(285): WP_Optimize->include_template()
    #7 /wp-includes/class-wp-hook.php(307): WP_Optimize_Minify_Admin->output_advanced()
    #8 /home/tlguzfgc/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    #9 /wp-includes/plugin.php(476): WP_Hook->do_action()
    #10 /wp-content/plugins/wp-optimize/includes/class-wp-optimize-admin.php(159): do_action()
    #11 /wp-content/plugins/wp-optimize/includes/class-wp-optimize-admin.php(108): WP_Optimize_Admin->display_admin_page()
    #12 /wp-includes/class-wp-hook.php(307): WP_Optimize_Admin->display_admin()
    #13 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    #14 /wp-includes/plugin.php(476): WP_Hook->do_action()
    #15 /wp-admin/admin.php(259): do_action()
    #16 {main}
    thrown

    @davidblood Could you please edit wp-config.php file and

    Replace

    define('WP_DEBUG', false);

    with this:

    ini_set('log_errors','On');
    
    ini_set('display_errors','Off');
    
    ini_set('error_reporting', E_ALL );
    
    define('WP_DEBUG', false);
    
    define('WP_DEBUG_LOG', true);
    
    define('WP_DEBUG_DISPLAY', false);

    Let us know if replacing with the above lines the warnings goes away?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Trying to access array offset on value of type null in’ is closed to new replies.