• 99w

    (@ninetyninew)


    Hi,

    We are developers of a number of extensions for WooCommerce, we have seen a few support requests lately, which are being caused by the iubenda plugin, specifically either the automatic blocking (which doesn’t appear to be able to be disabled), and/or native blockings feature.

    I am aware the automatic blocking is stated as an experimental feature as per this documentation: https://www.iubenda.com/en/help/133036-prior-blocking-of-cookies-automatic-blocking-auto-blocking, but would like to flag some issues it is causing, in a hope that you can consider rectifying how the automatic blocking is working, as in the current state, it can break inline JavaScript. That combined with this experimental feature seemingly being on by default it is effecting a number of websites (we just installed the plugin and it immediately causes the issues below).

    Here are a few examples of the issue, e.g. if you have inline JS that does this:

    $( '<a href="#" id="wcrp-rental-products-add-to-order-6638e3421f57e" class="wcrp-rental-products-add-to-order single_add_to_cart_button button ">Add to order #' + addRentalProductsPopupOrderId + '</a>' ).insertBefore( $( '#wcrp-rental-products-rental-form-wrap-6638e3421f57e' ).find( '.cart button[type="submit"]' ) );

    Then the result with iubenda active and the native blocking is this:

    $( '<a href="#" id="wcrp-rental-products-add-to-order-6638e39eed7af" class="wcrp-rental-products-add-to-order single_add_to_cart_button button ">Add to order #' + addRentalProductsPopupOrderId + '' ).insertBefore( $( '#wcrp-rental-products-rental-form-wrap-6638e39eed7af' ).find( '.cart button[type="submit"]' ) );

    Note in the above that the </a> has been removed.

    Another example, if you have inline JS like this:

    $( '<div id="wcrp-rental-products-availability-checker-auto-population-information-6638e3421f57e" class="wcrp-rental-products-availability-checker-auto-population-information wcrp-rental-products-information">' + rentalFormrentalFormAvailabilityCheckerPopulationInformation + ' <a href="/wordpress/product/hoodie-with-logo/?wcrp_rental_products_availability_checker_reset=1">Reset?</a></div>' ).insertAfter( $( '#wcrp-rental-products-rental-dates-wrap-6638e3421f57e' ) );

    Then the result with iubenda active and the native blocking is this:

    $( '<div id="wcrp-rental-products-availability-checker-auto-population-information-6638e39eed7af" class="wcrp-rental-products-availability-checker-auto-population-information wcrp-rental-products-information">' + rentalFormrentalFormAvailabilityCheckerPopulationInformation + ' <a href="/wordpress/product/hoodie-with-logo/?wcrp_rental_products_availability_checker_reset=1">Reset?</script>
    </form>
    </div>' ).insertAfter( $( '#wcrp-rental-products-rental-dates-wrap-6638e39eed7af' ) );

    Note in the above that the </a> has been removed, and has been replaced with a </script></form>, which breaks the JavaScript on the page, and outputs any further inline JS after this directly in the page as HTML.

    Thank you,

    • This topic was modified 2 months ago by 99w.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support micheleiub

    (@micheleiub)

    Hi there,

    Would it be possible for you to provide an example page where autoblocking is active and we can see the issue?

    If you are an Iubenda “paying” customer (users under a PRO/Ultra/Essential/Ultimate/Advanced plan) reach us by opening a support ticket on http://www.iubenda.com or sending your request to info@iubenda.com.

    Otherwise please reply on this thread.

    Thread Starter 99w

    (@ninetyninew)

    Here is an example URL on a sandbox: https://levelnation.s3-tastewp.com/product/test/

    Note this sandbox will expire in around 3 days.

    The changes highlighted above in our first message are the reasons why the script is being output in the HTML of the page, this page works fine, but when iubenda was installed, it then does this, after enabling the default settings for “Privacy Controls and Cookie Solution”, if you disable the native blocking setting, it works again.

    Plugin Support daniub

    (@daniub)

    Hi,

    we have found that the issue is related to the first parsing engine of the Native blocking (not the autoblocking, that is a different feature you can enable on iubenda.com dashboard) and we are investigating how to solve the issue.

    In the meantime you can switch parsing engine in our plugin, if you want to keep native blocking active.

    • In the Cookie Solution area of our plugin, click “Configure”;
    • You can switch the parsing engine from primary to secondary. Screenshot: https://prnt.sc/hjGRbdF7rr03

    Hope this helps!

    • This reply was modified 2 months ago by daniub.
    Thread Starter 99w

    (@ninetyninew)

    @daniub thanks for investigating and noting you can replicate the issue, can you keep me updated on this thread when a new version with a fix for this maybe available.

    Thank you,

    Thread Starter 99w

    (@ninetyninew)

    Hi,

    Do you have any updates on the progress of this fix? As we’ve noticed there have been 2 new releases since then and wanted to check if included in those?

    Thank you,

    Plugin Support daniub

    (@daniub)

    Hi @ninetyninew,

    I apologize for the delay, but the recent release does not include this particular fix.

    We will inform you as soon as the fix is released. In the meantime, please consider using the provided workaround.

    Thank you for your understanding and cooperation.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.