• Resolved Thomas Endersen

    (@thehinesgaphideaway)


    The latest update is causing a fatal error!!

    [30-Nov-2023 15:11:55 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_id() on bool in /home/royalcoa/public_html/wp-content/plugins/product-blocks/addons/compare/Compare.php:242
    Stack trace: 0 /home/royalcoa/public_html/wp-content/plugins/product-blocks/addons/compare/Compare.php(595): WOPB\Compare->product_list() 1 /home/royalcoa/public_html/wp-content/plugins/product-blocks/classes/Initialization.php(210): WOPB\Compare->product_list_modal() 2 /home/royalcoa/public_html/wp-content/plugins/product-blocks/classes/Initialization.php(170): WOPB\Initialization->compare_modal_wrap() 3 /home/royalcoa/public_html/wp-includes/class-wp-hook.php(324): WOPB\Initialization->footer_modal_callback() 4 /home/royalcoa/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 5 /home/royalcoa/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Thomas Endersen

    (@thehinesgaphideaway)

    For now as a quickfix, I had to add:

    if (!$product) continue;

    before line 242.

    Thread Starter Thomas Endersen

    (@thehinesgaphideaway)

    Also, I had to turn off the Compare addon since it also breaks when a compare is tried on the front end, it merely shows a blank overlay and then all UI breaks and can’t click on anything. A page refresh is needed.

    bestbusweb

    (@bestbusweb)

    I’m having the same problem, causing the fatal error as well.

    Mehedi

    (@mehedi7970)

    Hello @thehinesgaphideaway, @bestbusweb,

    Thank you for bringing this issue to our notice. We already found this issue. In our next update, it will be fixed.

    Tonmoy

    (@azimkhan123)

    Hi @thehinesgaphideaway & @bestbusweb,

    We already released an update to fix this issue. Please update your site with the latest version of ProductX (3.1.2). That will solve the issue permanently.

    Thank you for your patience!

    Thread Starter Thomas Endersen

    (@thehinesgaphideaway)

    Thanks, I can confirm the issue is resolved.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘CRITICAL ERROR!! Breaks Whole Site!’ is closed to new replies.