Widget not showing; javascript errors

Regarding the [wc-blocks-checkout] warning, I’m not sure why it’s coming up on pages that have nothing to do with the checkout (e.g. the landing page). I do have a plugin that adds a side-cart widget which allows users to view their cart contents and proceed to checkout from the side cart pop-out.

Hi,

Thank you for reaching out and providing detailed information about the issue.

Regarding the dependency warning related to [wc-blocks-checkout], we’re aware of this and will be addressing it in the next release.

Secondly, for the JavaScript error, as we couldn’t reproduce it on our end, could you please help us by providing a screencast showing how the issue occurs? Additionally, it would be helpful to know the versions of PHP, WordPress, and WooCommerce you’re using.

Please submit this information by opening a support ticket using the following link: WPLoyalty Support.

We’ll look into this promptly and assist you further.

Best regards,
Akshaya
WPLoyalty Support Team

Actually, I think the root cause of the issue may be coming from this snippet. This is the final few lines of bundle.js file:

var Z = document.getElementById(“wll-site-launcher”);
Z ? t.createRoot(Z).render(e.createElement(X, null)) : setTimeout((function() {
Z = document.getElementById(“wll-site-launcher”);
var n = t.createRoot(Z);
Z && n.render(e.createElement(X, null))
}
), 1e3)

The above script attempts to create the widget via the ‘wll-site-launcher’ DOM element. But it may happen that the element is not yet created, so the script has a fallback where it defers this action by one second (1e3 milliseconds in the original code). On a slow site with a complex DOM (think elementor and lots of featured products on the home page), a one second delay is not enough, and the callback fails because the element it’s looking for is still not created. This is what I see in the error: the argument passed to createRoot() is in fact null.

I manually changed the timer to two seconds (2e3) and this seems to help on my sites, but this is not the right way to do it. The code should keep checking for null and re-defer itself until the DOM is ready. Perhaps do this up to 10 times, deferring another second each time, and then print an error message and fail gracefully. I’m not a JS developer so I can’t suggest anything better, sorry.

Hi,

Thank you for sharing these details!

We understand the issue you’re facing with the wll-site-launcher element not being created in time due to slow loading.

We’ll be addressing this in the next release to ensure the widget loads correctly even on slower sites.

Thanks for bringing this to our attention, and if you have any other questions or concerns, feel free to reach out!

Regards,

WPLoyalty Support Team.

Hi there,

Since we haven’t received a response, we’ll consider this issue resolved. If you need further assistance or have any questions, feel free to reach out to us.

Our support team is always here to help.

Thanks!