Steve

Thanks again for your message and time Abu,

Yes, that’s how I’ve displayed reviews; with the shortcode widget.

So I’m certain it’s a .js conflict. I’ve tested placing the shortcode in the Hello theme’s main body content area instead of the footer (where It’s always been for me). It will display as intended on the front end page view, but note, it does does still a preview in Elementor’s builder window with the ‘extra content’.

Seems like a jquery order firing conflict using Elementor ‘Pro’. It obviously changes the js content and firing order with the added ‘section’ code for a global footer.

I believe you are seeing everything without issue because the default free theme does not include any footer section at all, (although I do not have any experience with the Hello theme and cannot find a place to set a footer anywhere without Pro).
?
I have copied a third staging enviro if you would still like to investigate further. Let me know where i can safely send you admin access details.

I still have the site set to Hello theme, and TWB Reviews/Woocommerce plugins only.

I hope you’re remaining safe and well.

Hi again Abu,

Thanks for your time and reply.

The failed font loading requests are only occurring as a result of testing other Elementor theme processes since discovering this issue 7 days ago. I am constantly running through many testing/problem-solving combinations. I can’t afford the time to leave the testing site in a static state while I possible reply comes. I do need to continue to meet our deadline for re-dev.
Just before sending my first message I began hosting site fonts locally and everything worked fine. I then experimented using Elementor to design a theme header to see how things react. After doing a GTMetrix scan I also noticed that this broke the font loading process. Please note this has no bearing on the thoroughly tested results of this issue prior.

I have tested this thoroughly and confident it’s a conflict between Elementor and TWB.

Aside from many other test processes performed, I have stripped everything back to the barebones native ‘Hello’ theme from Elementor, woocommerce and TWB. I have also tested this on 4 different themes and the results are the same regardless. The only time the page content displays in TWB’s slider container window is on the two pages which use the Elementor Builder for it’s main page content display. Every other non-Elementor page does not do this.

I’ll look into deferring TWB scripts at a later time. Thank you.

Hope this helps.

Steve

Hi there, thank you for your response.

Yes it does. Although what appears to happen (as it did just now when tested again) is that once I switch JScombine off then back on again and ‘Purge All’, it begins working on all devices. However this happens only for a while then randomly stops working weeks or months later.

The challenge for me as a really time challenged small biz owner is that I don’t often know when the phone/tablet form stops working again until we get a heads up from a customer. It’s all very random. I can get a customer email us saying it’s not working on their iPhone, but then I test on my phone, an android tablet and our iPhone I discover it it’s still working for us.

It’s obviously hit and miss with JS firing order conflicts.

Does this mean the only reliable solution (without custom coding the complete DIVI JS firing order) is to keep JS combine and JS minify permanently disabled in Litespeed?

Thanks for your time and help.

Hi again,

A quick update:
If I turn off the ‘JS Combine’ in the page optimization settings the contact form works on desktop size screens, but still does not begin working on screens less than 980px until I deactivate Litespeed.
Could this be fixed with an ESI or is it possible there something else more sinister going on in the code?

Regards