Phil

Thanks for the reply. I will raise a ticket with Formidable Forms to sort this out.

Thanks, I think I will use the JS Layout mode for now and look into this again later. ??

Hi Sayontan,

Thank you for the detailed reply and suggestions.

I use the Litespeed Cache plugin, which enables lazy loading, but disabling this plugin and every other non-critical plugin does not resolve the issue. I do not think the Underscores theme uses lazy loading, either.

For some reason, the browser displays the image placeholder and alt text as if the image cannot be loaded until it is. The issue appears in Chrome and Firefox, so it is not browser-specific.

Switching to the JS layout engine resolves the issue because of the different loading methods used. I will consider using the JS layout engine, but I prefer the CSS method.

A demo gallery with Litespeed Cache disabled is here:

https://staging.simplicitytheme.com/abstract-paintings/

I have spent time trying to debug this, but I can’t see where the problem lies. I understand the issue might be specific to my theme and difficult to resolve. Thanks.

Awesome thanks, we will test it out ??

Hi Zorem,

Any updates on this solution?

Thanks,

Phil.

Thanks Zorem, that would be great.

A selector that let’s us map the customer carrier to a supported carrier would do fine.

Phil.

Hi Zorem,

Right but I don’t think that’s possible, the third-party is a large dropship company based in China and will not make minor changes at our request. Can you provide another solution please? Surely this can be address via a WP function or similar? I think the plugin should be able to handle this scenario.

Thanks,

Phil.

Great, thanks!

Hi Zorem,

Thanks for the quick reply.

Just to clarify we have a third party providing tracking numbers via the WooCom REST API, when the tracking number is added AST says ‘Shipping provider not found’ on the orders page.

Screenshot here

Are you saying that if we just rename the existing shipping providers it will solve this problem?

Thanks,

Phil.

Hi Jordy,

Thanks for the reply, it’s clear for me now that the plugin operates at the ‘media entry’ level and not the ‘media size’ level. I think why I got confused is because of all the talk about removing ‘thumbnails’, maybe something to look at there.

Regards,

Phil.

Hi, yes it was a caching issue but more to do with our CDN caching I believe. I think we have sorted it out now. ??

Hi, I’ve sent the requested details via the contact form, hopefully it went through OK as there was no confirmation message after submitting the issue. Thanks, Phil.