Forum Replies Created

Viewing 15 replies - 1 through 15 (of 341 total)
  • Same error on staging site:

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 237 der Datei /wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php verursacht. Fehlermeldung: Uncaught Error: Class “Automattic\WooCommerce\Enums\DefaultCustomerAddress” not found in /wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php:237

    Thread Starter fox-didl

    (@fox-didl)

    Hi. I tested with your RC2 and yes, this version is recognizing product bundles and so the pay button is there at product page and it is possible to press it. And yes, the payment-process with a window is starting aswell, but at the end it it breaking. Just ordering the product bundles at checkout page is working with Apple Pay and Google Pay.

    So, yes it is better. But still not a final working solution.

    Update – complete working solution found

    After further analysis, the two-bug fix I described earlier was not sufficient. The Brevo CDN SDK (sdk-loader.js) autonomously initializes WonderPush based on the server-side Brevo account configuration, regardless of what PHP options are passed. Simply omitting service_worker_url and push from brevo_init_options() does not prevent the CDN SDK from triggering the WonderPush ServiceWorker chain.

    A third fix is required: intercept navigator.serviceWorker.register at the browser level, before the Brevo SDK loads, so that any ServiceWorker registration attempt for the Brevo plugin scope is silently blocked.

    The complete working patch requires changes to three files plus a functions.php filter:

    1. inc/push-utils.php – is_push_sdk_enabled()

    Add at the very beginning of the method:

    php

    if ( get_option( ‘sib_push_sdk_force_disabled’, ‘0’ ) === ‘1’ ) {

    return false;

    }

    2. inc/push-utils.php – brevo_init_options()

    Wrap all push-related keys (pushservice_worker_urlframe_url) in a conditional so they are only included when push is actually enabled:

    php

    $options = array( ‘client_key’ => $ma_key, ’email_id’ => $ma_email );

    if ( self::is_push_sdk_enabled() ) {

    $options[‘push’] = $push_options;

    $options[‘service_worker_url’] = ‘…’;

    $options[‘frame_url’] = ‘brevo-frame.html’;

    }

    return $options;

    3. sendinblue.php – install_ma_script()

    Output the following JavaScript before the Brevo SDK <script> tag when push is disabled. This patches navigator.serviceWorker.register so the CDN SDK cannot autonomously register WonderPush, and also cleans up any previously cached ServiceWorker:

    javascript

    (function() {

    if (‘serviceWorker’ in navigator) {

    var _origRegister = navigator.serviceWorker.register.bind(navigator.serviceWorker);

    navigator.serviceWorker.register = function(scriptURL, options) {

    if (typeof scriptURL === ‘string’ &&

    scriptURL.indexOf(‘woocommerce-sendinblue-newsletter-subscription’) !== -1) {

    // Return forever-pending Promise: WonderPush waits silently, no console errors

    return new Promise(function() {});

    }

    return _origRegister(scriptURL, options);

    };

    // Unregister any previously installed Brevo ServiceWorker from browser cache

    navigator.serviceWorker.getRegistrations().then(function(registrations) {

    registrations.forEach(function(sw) {

    if (sw.scope && sw.scope.indexOf(‘/woocommerce-sendinblue-newsletter-subscription/’) !== -1) {

    sw.unregister();

    }

    });

    });

    }

    })();

    4. functions.php (theme) – activate the override

    php

    add_filter( ‘pre_option_sib_push_sdk_force_disabled’, function() { return ‘1’; } );

    Why new Promise(function() {}) instead of Promise.reject()? WonderPush does not gracefully handle a rejected registration promise in all code paths, producing an Uncaught (in promise) error in the console. A forever-pending Promise causes WonderPush to wait silently without errors.

    Verified on: Plugin version 3.3.4, WP 6.x. All wonderpush.min.jssdk-loader.js and sibautomation.com errors are gone after this patch.

    Root cause summary for the Brevo developers:

    1. is_push_sdk_enabled() uses a 30-day transient cache → deactivation via the UI has no immediate effect
    2. brevo_init_options() always passes push parameters to the MA SDK → SDK initializes WonderPush autonomously
    3. The MA CDN SDK reads account-level push config from Brevo’s API → push initializes regardless of PHP options

    All three layers need to be addressed for a proper fix.

    Same issue here. I did a deeper analysis of the root cause – there are actually two bugs that must be fixed together. I did the following update and now it’s working fine. Please update the plugin asap.

    The workaround from @kiwifraise ($push_enabled = false; in sendinblue.php) fixes the WonderPush standalone SDK block, but the ServiceWorker errors still persist because brevo_init_options() always passes service_worker_urlpush, and frame_url to the Brevo Marketing Automation SDK – which then internally initializes WonderPush on its own.

    Bug 1 – is_push_sdk_enabled() in inc/push-utils.php uses a 30-day transient cache (get_push_application(30 * 86400)). When you deactivate push in the UI, the cached value stays true for up to 30 days. The deactivation setting is simply ignored.

    Bug 2 – brevo_init_options() in inc/push-utils.php always includes service_worker_url and push in the init object passed to the MA SDK, even when push is deactivated. The MA SDK sees service_worker_url and internally activates WonderPush – producing the same ServiceWorker errors even after Bug 1 is fixed.

    Working solution (no plugin file edits needed after this):
    1. In inc/push-utils.php, add a guard at the top of is_push_sdk_enabled():

    if ( get_option( 'sib_push_sdk_force_disabled', '0' ) === '1' ) return false;

    1. In brevo_init_options(), wrap the push-related keys (pushservice_worker_urlframe_url) in a check so they are only included when push is actually enabled.
    2. In functions.php of your theme (no DB changes required):

    add_filter( 'pre_option_sib_push_sdk_force_disabled', function() { return '1'; } );

    This stops both the standalone WonderPush block AND the MA SDK from initializing the ServiceWorker.

    A proper fix in the plugin should set a local WordPress option when the user deactivates push in the settings UI, rather than relying solely on the WonderPush API + a 30-day cache.

    Status: confirmed on plugin version 3.3.4, WP 6.x.

    • This reply was modified 1 month, 1 week ago by fox-didl.
    • This reply was modified 1 month, 1 week ago by fox-didl.
    Thread Starter fox-didl

    (@fox-didl)

    Try to reinstall 10.5 again. But no change after.

    [07-Feb-2026 09:53:30 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_name() on false in /wp-content/plugins/woocommerce/templates/dashboard-widget-reviews.php:39
    Stack trace: 0 /wp-content/plugins/woocommerce/includes/wc-core-functions.php(346): include() 1 /wp-content/plugins/woocommerce/includes/admin/class-wc-admin-dashboard.php(517): wc_get_template(‘dashboard-widge…’, Array) 2 /wp-admin/includes/template.php(1453): WC_Admin_Dashboard->recent_reviews(”, Array) 3 /wp-admin/includes/dashboard.php(280): do_meta_boxes(Object(WP_Screen), ‘column4’, ”) 4 /wp-admin/index.php(204): wp_dashboard() 5 {main}

    thrown in /wp-content/plugins/woocommerce/templates/dashboard-widget-reviews.php on line 39

    Reverting back und everything fine again now. Waiting for bugfix 10.5.1.

    Thread Starter fox-didl

    (@fox-didl)

    This is correct. Example like here. This would be great to habe at the right sidebar at WooCommerce procuts, pages and posts at classic editor and block editor sidebar aswell.
    https://prnt.sc/gvb4yxk9635e

    And to import existing data, would be also amazing.

    Thread Starter fox-didl

    (@fox-didl)

    Thanks for the information.

    2.0.3 working
    2.0.4 up to 2.0.7 not working – no status there anymore

    Woocommerce 10.4.3
    Subscriptions 8.2.1

    I can send you a status report with all plugins. But how?

    Thread Starter fox-didl

    (@fox-didl)

    Got again an update for a developer version which already solved some issues. And now have been updated again to solve this new issue with your plugin aswell. The rollout of the new version will be soon as far as I know.

    Thread Starter fox-didl

    (@fox-didl)

    got an beta-update for fluid checkout. working now. thanks a lot.

    • This reply was modified 6 months, 2 weeks ago by fox-didl.
    Thread Starter fox-didl

    (@fox-didl)

    Thanks. This helped – webhooks.

    Thread Starter fox-didl

    (@fox-didl)

    Sure. done – sent.

    Thread Starter fox-didl

    (@fox-didl)

    I just have this for you:
    https://uxthemes.com/support/

    But I also have a staging site for you if this is helpful.

    Thread Starter fox-didl

    (@fox-didl)

    On Burst Statistics page only. Otherwise I would not have informed you.

    Thread Starter fox-didl

    (@fox-didl)

    Thanks for the upate. There is one more little issue here – I think CSS.

    Maybe you can fix this so everything is in one line as it should be.
    https://prnt.sc/3ZHTHiWBnCuK

    Thread Starter fox-didl

    (@fox-didl)

    Sorry, there is a difference. Tested again – with 1.1.1 working and with 1.1.3 not working. Thats it.

    Ticket 2xxxx7 and 2xxxx8 including a video.

Viewing 15 replies - 1 through 15 (of 341 total)