• Resolved sofie1ele

    (@sofie1ele)


    Hi,

    This bug is going on for many months already. When I have woocommerce, and I edit ELementor page as SHOP MANAGER, I get a fatal error (500 error).

    When I deactivate BOOSTER, the issue is gone.

    I had the same issue on many many websites already, some very simple, so the main issue is Booster.

    Please help resolve this big Booster bug, it’s ALWAYS happening, even in very basic installations

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Contributor David G

    (@gravid7)

    Hi @sofie1ele,

    Thanks for reaching out to us.

    The issue appears to be related to user role permissions, specifically a conflict between the Shop Manager role and Booster when using Elementor.

    Could you please contact us via our website? This will allow us to take a deeper look and assist you further. In the meantime, granting additional permissions to the Shop Manager role may resolve the issue.

    Thread Starter sofie1ele

    (@sofie1ele)

    Hi,

    This issue is happening almost for a year now!

    It happens on ALL woocommerce + Elementor + Booster, and it’s completely caused by Booster. When disabling Booster it’s solved.

    So you can simulate this major fatal error easily.

    Please let me know exactly which permissions and where I have to add it to the SHOP MANAGER role.

    Thanks

    Plugin Contributor David G

    (@gravid7)

    Hi @sofie1ele,

    Thanks for your message.

    Could you please contact us via our website? This will allow us to take a deeper look and assist you further.

    Thread Starter sofie1ele

    (@sofie1ele)

    Hi,

    Have you tested the most BASIC installation: WP + Woocommerce + Elementor + Booster. It ALWAYS gives a fatal error due to Booster big bug!

    Why keep pushing me to contact via the website ? Why not checking yourself and give the solutions here so that anybody facing this major issue can be helped ?

    I have a lifetime Booster subscription, I am very disappointed. I already deleted Booster on several websites, because of those major Booster + Elementor errors for the shop manager. So contacting you via your website is pointless, as I deleted Booster on those sites!

    Just take 4m of your time, test it on the most basic installation, and see how you can fix the Booster 500 error for shop manager in woocommerce with Elementor.

    THANK you for your help(?)

    Plugin Author Pluggabl

    (@pluggabl)

    Hi @sofie1ele

    Thank you for your persistence and the detailed report. I apologize for the frustration this has caused. We value you as a lifetime customer, and a recurring fatal error is unacceptable.

    We are now setting up a clean test environment with Elementor and WooCommerce to replicate the behavior. Because we’re building this environment from scratch to find the core issue, it’s a more detailed process than analyzing an existing site directly.

    To help us accelerate the diagnosis, if you have a moment to check a few things on a staging site, the information would be invaluable.

    • Fatal Error Log: The most helpful item is the specific error message. If you enable WP_DEBUG_LOG in your wp-config.php file and trigger the error, the message from the debug.log file in /wp-content/ would tell us exactly where the code is breaking.
    • Isolate the Module: You could also try deactivating all Booster modules and then re-enabling them in small groups to see which specific one triggers the error.
    • Permissions Test: As a temporary workaround, you could grant the edit_theme_options capability to the Shop Manager role to see if that resolves the conflict with the page builder.

    We are still proceeding with our own replication, but any details you can provide would be very helpful.

    Thank you for your patience while we investigate.

    Thread Starter sofie1ele

    (@sofie1ele)

    Hi,

    I appreciate your effort in solving your bug, as I bought a lifetime Booster access, and I do not think it’s my job to pay for support to solve a native Booster bug, that affects lots of people and all my own sites.

    Adding edit_theme_options capability did not solve the issue. I disabled all plugins and enabled one by one: Booster module is the issue.

    Here you have the debug.log:

    [15-Jul-2025 09:46:54 UTC] PHP Fatal error:  Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, true given in /home/test.be/wp-content/plugins/elementor/includes/widgets/heading.php:132
    Stack trace:
    #0 /home/test.be/wp-content/plugins/elementor/includes/widgets/heading.php(132): array_filter()
    #1 /home/test.be/wp-content/plugins/elementor/modules/content-sanitizer/module.php(37): Elementor\Widget_Heading->sanitize()
    #2 [internal function]: Elementor\Modules\ContentSanitizer\Module->Elementor\Modules\ContentSanitizer\{closure}()
    #3 /home/test.be/wp-content/plugins/elementor/includes/db.php(265): call_user_func()
    #4 /home/test.be/wp-content/plugins/elementor/includes/db.php(269): Elementor\DB->iterate_data()
    #5 /home/test.be/wp-content/plugins/elementor/includes/db.php(262): Elementor\DB->iterate_data()
    #6 /home/test.be/wp-content/plugins/elementor/includes/db.php(269): Elementor\DB->iterate_data()
    #7 /home/test.be/wp-content/plugins/elementor/includes/db.php(262): Elementor\DB->iterate_data()
    #8 /home/test.be/wp-content/plugins/elementor/includes/db.php(269): Elementor\DB->iterate_data()
    #9 /home/test.be/wp-content/plugins/elementor/includes/db.php(262): Elementor\DB->iterate_data()
    #10 /home/test.be/wp-content/plugins/elementor/includes/db.php(269): Elementor\DB->iterate_data()
    #11 /home/test.be/wp-content/plugins/elementor/includes/db.php(269): Elementor\DB->iterate_data()
    #12 /home/test.be/wp-content/plugins/elementor/modules/content-sanitizer/module.php(35): Elementor\DB->iterate_data()
    #13 /home/test.be/wp-includes/class-wp-hook.php(324): Elementor\Modules\ContentSanitizer\Module->sanitize_content()
    #14 /home/test.be/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #15 /home/test.be/wp-content/plugins/elementor/core/base/document.php(823): apply_filters()
    #16 /home/test.be/wp-content/plugins/elementor/core/documents-manager.php(548): Elementor\Core\Base\Document->save()
    #17 [internal function]: Elementor\Core\Documents_Manager->ajax_save()
    #18 /home/test.be/wp-content/plugins/elementor/core/common/modules/ajax/module.php(176): call_user_func()
    #19 /home/test.be/wp-includes/class-wp-hook.php(324): Elementor\Core\Common\Modules\Ajax\Module->handle_ajax_request()
    #20 /home/test.be/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #21 /home/test.be/wp-includes/plugin.php(517): WP_Hook->do_action()
    #22 /home/test.be/wp-admin/admin-ajax.php(192): do_action()
    #23 {main}
    thrown in /home/test.be/wp-content/plugins/elementor/includes/widgets/heading.php on line 132
    Plugin Author Pluggabl

    (@pluggabl)

    Hi @sofie1ele

    You are 100% right. We do not expect any customer, especially a lifetime user, to pay to have a core bug fixed.

    Our regular plugin updates consistently include fixes for issues reported by users, compatibility updates from changes in WordPress and WooCommerce, and bugs found by our own team. While all new feature development is now focused on the Booster Elite version, ensuring the core plugin is stable for our entire community remains a fundamental priority.

    This debug log is extremely helpful. David (@gravid7) will take it from here to complete the analysis and will update you in this thread with his findings and the plan for a fix.

    Thank you for your patience.

    Plugin Contributor David G

    (@gravid7)

    Hi @sofie1ele,

    We’ve identified a conflict between Booster and Elementor causing the 500 error.

    Our team is working on a fix and testing it in a controlled environment.

    Thread Starter sofie1ele

    (@sofie1ele)

    Hi,

    I really appreciate the effort and the investigation… I await patiently this fix, which will benefit lots of other Booster users…

    Please keep me posted!

    Plugin Contributor David G

    (@gravid7)

    Hi,

    We’ve tested the basic setup (WordPress + WooCommerce + Elementor + Booster) on our end and are not able to reproduce the fatal error you’re experiencing. This suggests the issue might be related to your specific site configuration, settings, or environment.

    To investigate and fix this properly, we would need to debug the issue directly on your site. Without seeing the exact setup where the error occurs, it’s very difficult for us to identify the root cause and provide a reliable fix.

    We kindly request you to contact us through our official support portal:
    https://booster.io/contact-us/

    Please note: You will not be asked for any payment for bug fixing or support related to Booster Core. We offer this support free of charge, even for lifetime license holders like yourself.

    We truly appreciate your patience and cooperation. Please do reach out via the support form, and if possible, share temporary access or staging credentials so we can debug directly and resolve this quickly for you and for others who might be affected.

    Thank you again for your continued support.

    Thread Starter sofie1ele

    (@sofie1ele)

    Hi,

    David G (@gravid7) 5 days ago

    Hi @sofie1ele,

    We’ve identified a conflict between Booster and Elementor causing the 500 error.

    Our team is working on a fix and testing it in a controlled environment.

    5 days ago you admit there is a fatal error bug of Booster & Woocommerce with Elementor :

    Now you suddenly switch and say there is no bug ? This is very strange indeed …

    I have just contacted you through your website, and with my UNLIMITED booster account I paid for. You get full access and you can test yourself. Even when deactivating all plugins, and just basic theme, BOOSTER gives the 500 ERROR when Saving Elementor edit page as shop manager. You have surely experienced this also, as you stated it 5 days ago that you saw this bug too… @David G 

    best regards

    Thanks

    Plugin Contributor David G

    (@gravid7)

    Hi @sofie1ele

    I’ve resolved the issue.

    The conflict was caused by the file:
    /includes/functions/wcj-functions-general.php

    I’ve updated the wcj_add_allowed_html() function to prevent conflict with Elementor.

    here you can check updated code funcation : https://drive.google.com/file/d/1vYwN68iS6PutJS4cYY7cRF_oxltwLYOO/view?usp=sharing

    Please review the changes and confirm if everything is working fine on your end.

    Thread Starter sofie1ele

    (@sofie1ele)

    Hi, this file: /includes/functions/wcj-functions-general.php is a standard wordpress file, that is not changed by my nor by any plugin or theme. So are you saying I have to change a wordpress core file ?

    So is it possible that you update the Booster plugin, so it is compatible ? It is never wise to change wordpress core files, as in any updates this get overriden and this is not good practice for security and bug-prevention.

    thanks

    Thread Starter sofie1ele

    (@sofie1ele)

    Thank you so much, it was not a WP core file, but a Booster file.

    I just had to do a small change in /wp-content/plugins/booster-plus-for-woocommerce/includes/functions/wcj-functions-general.php

    By updating this wcj_add_allowed_html function (around line 1068) to this

    if ( ! function_exists( 'wcj_add_allowed_html' ) ) {
    /**
    * Wcj_add_allowed_html.
    *
    * @version 7.2.5
    * @since 5.6.0
    * @param array $allowed_html to get default allowed html.
    * @param string $context to get default context.
    */
    function wcj_add_allowed_html( $allowed_html, $context ) {

    // If Elementor is running (editor, ajax, REST), bail early.
    if (
    ( isset( $_REQUEST['action'] ) && strpos( $_REQUEST['action'], 'elementor' ) !== false ) ||
    ( isset( $_SERVER['REQUEST_URI'] ) && strpos( $_SERVER['REQUEST_URI'], '/elementor' ) !== false )
    ) {
    return $allowed_html; // Don't touch anything.
    }

    $allowed_extra_html = array(
    'input' => array(
    'type' => true,
    'name' => true,
    'value' => true,
    'id' => true,
    'checked' => true,
    'class' => true,
    'style' => true,
    'placeholder' => true,
    'dateformat' => true,
    'mindate' => true,
    'maxdate' => true,
    'excludemonths' => true,
    'excludedays' => true,
    'firstday' => true,
    'display' => true,
    'required' => true,
    'min' => true,
    'max' => true,
    'disabled' => true,
    'step' => true,
    'changeyear' => true,
    'yearrange' => true,
    'timeformat' => true,
    'interval' => true,
    'readonly' => true,
    'data-blocked_dates' => true,
    'currentday_time_limit' => true,
    'data-blocked_dates_format' => true,
    'accept' => true,
    'data-*' => true,
    'attribute_*' => true,
    'variation_id' => true,
    'size' => true,
    'maxlength' => true,
    ),
    'textarea' => array(
    'name' => true,
    'value' => true,
    'id' => true,
    'class' => true,
    'style' => true,
    'placeholder' => true,
    'required' => true,
    'disabled' => true,
    'autocomplete' => true,
    'maxlength' => true,
    ),
    'select' => array(
    'multiple' => true,
    'name' => true,
    'class' => true,
    'id' => true,
    'style' => true,
    'size' => true,
    'disabled' => true,
    'type' => true,
    'required' => true,
    ),
    'option' => array(
    'value' => true,
    'style' => true,
    'selected' => true,
    'class' => true,
    'disabled' => true,
    ),
    'span' => array(
    'id' => true,
    'style' => true,
    'class' => true,
    'data-tip' => true,
    'disabled' => true,
    ),
    'td' => array(
    'style' => true,
    'class' => true,
    ),
    'tr' => array(
    'id' => true,
    'style' => true,
    'class' => true,
    ),
    'th' => array(
    'scope' => true,
    'style' => true,
    'class' => true,
    ),
    'label' => array(
    'style' => true,
    'class' => true,
    ),
    'p' => array(
    'class' => true,
    'style' => true,
    ),
    'button' => array(
    'style' => true,
    'class' => true,
    'disabled' => true,
    'wcj_data' => true,
    'fdi' => true,
    'var_id' => true,
    'customeremail' => true,
    'customername' => true,
    'offerprice' => true,
    'wcj_bestprice_arr_key' => true,
    'is_variable' => true,
    'product_id' => true,
    'image_url' => true,
    ),
    'style' => array(
    'type' => true,
    ),
    'a' => array(
    'target' => true,
    'wcj-copy-data' => true,
    'currency_from' => true,
    'currency_to' => true,
    'start_date' => true,
    'end_date' => true,
    'input_id' => true,
    'start_date' => true,
    'is_variable' => true,
    'image_url' => true,
    'style' => true,
    'wcj_data' => true,
    ),
    'details' => array(
    'open' => true,
    ),
    'bdi' => true,
    'em' => true,
    'iframe' => array(
    'width' => true,
    'height' => true,
    'src' => true,
    'frameborder' => true,
    'allow' => true,
    'allowfullscreen' => true,
    ),
    );
    $allowed_merged_html = array_merge_recursive( $allowed_html, $allowed_extra_html );
    return $allowed_merged_html;
    }
    add_filter( 'wp_kses_allowed_html', 'wcj_add_allowed_html', PHP_INT_MAX, 2 );
    }

    I trust this fix will be added in the next Booster update.

    Thank you for your GREAT support 🙂

    Now I can happily keep using Booster

    • This reply was modified 1 year ago by sofie1ele.
Viewing 14 replies - 1 through 14 (of 14 total)

The topic ‘Fatal error with Booster & Elementor for Shop Manager (urgent issue)’ is closed to new replies.