YaronE

Yes they are all installed (Latest), don’t know why the language doesn’t appear
As soon as I have time again, I’ll send you the other details, but hopefully will be able to reproduce the issue with the information I’ve provided

Hi

The interface you screenshot it doesn’t appear for me at all, there is no language interface, it doesn’t matter which language I choose before I click the add new feed button.

Here you go cf7 Submitted form arrives it arrived like this

View post on imgur.com

settings

View post on imgur.com

The two posters above me are obviously invested in the product, so they have a very specific perspective regarding this. also they miss categorize what I say And that’s fine, but to be clear.

When I wrote this review it was almost impossible to understand that this is a paid product, let me emphasize that there’s nothing wrong with having a paid product, a partially paid product, trial version, on up sale product, or any other type of mixed free/paid product.

It is common, and expected. the rating I’ve provided is solely regarding pre-installation clarity, and whether finding out after the installation should be a red flag for user trust. for me it is.

I also acknowledged that the whole thing could be an oversight by the development team, But the comments above leads me to lean toward this being a marketing strategy, maybe it is maybe it isn’t, I can only comment on the end result.

There was a similar post in dealing with this issue
https://www.ads-software.com/support/topic/exclude-user-agent-from-all-optimizations/

And that with and the help of Lars (From LiteSpeed)
This is the code I ended up using while they dig into the issue (top of wp-config.php)

// Added by me - 
if (stripos($_SERVER['HTTP_USER_AGENT'],"Instagram")!==false  ) {
 define( 'LITESPEED_DISABLE_ALL', true );
}

// END

There is no misunderstanding, the product is not fully functional and has a paid version,
which is almost impossible to know until you install it.

Any news ?

Hi @haseeb0001

Thanks for your response, I’m using the Gmail API (G Suite) with PostSMTP
As the Mailer Type, and the issue is specific with Emails that are sent from Contact Form 7 (used as the Site contact form)

When those forms are sent, they arrive in the inbox without the SPF, DKIM, or DMARC authentications.

Problem still exists even after the latest version v2.0.26

Any ideas what to do? or how to solve it?

Well I’m just gonna leave a solution for anybody who might be facing the same problem, I have ended up using a plug-in called “Disable Lazy Load”.

The author claims it’s a one line plug-in, This plug-in only disables the lazy load implementation of WordPress.

The way I see it it’s definitely a problem that should be addressed with lightspeed, lightspeed Shouldn’t conflict with core functionality, if the lazy loading is chosen by the user to be handled by lightspeed it should supersede the native lazy loading functionality which is basic.

At the current state the score functionality cancels any optimization done by Lightspeed lazy loading, Making the lightspeed lazy loading optimization useless since WP 5.5 even if it’s turned on.

I’ve purged the cash of the site, and cloud flare as well it does nothing
The attribute still remains when using the first code.

If I use this code instead of the other one it will remove loading=”lazy”
Everywhere, but it will remove litespeed cache lazy loading as well, While I’m trying to remove only the WordPress addition.

function disable_template_image_lazy_loading( $default, $tag_name, $context ) {
    if ( 'img' === $tag_name && 'wp_get_attachment_image' === $context ) {
        return false;
    }
    return $default;
}
add_filter(
    'wp_lazy_loading_enabled',
    'disable_template_image_lazy_loading',
    10,
    3
);

From what I have been able to gather, putting this in the functions.php file should prevent loading=”lazy” from appearing

add_filter( 'wp_lazy_loading_enabled', '__return_false' );

but it doesn’t seem to have any effect when I include it.

I would like lightspeed cash to control the behavior of lazy loading on the site, but in WordPress 5.9 LS excludes seems to be ignored for me

The funny thing is even if you had that piece of code

greeting_dialog_display='hide'

It still opens by default, and since it’s sitting here a week with no response it’s probably not going to be fixed anytime soon

That’s great,,, that’s what I wanted to know
it’s the equivalent of Regex https://site.com/.*

Adding a short explanation underneath the URL box in the plug-in could help explain how it handles exceptions better, if I remember correctly, currently it’s using the phrase “exact” URL that’s what threw me off, it gave me the impression that I need to enter the exact URL of each URL I want to exclude.

rather than just the root, to exclude the entire website.
thanks for the clarification ??

thanks for the comment,,, I also gave you five stars for the work you did on the plugin.
hopefully in the future you’ll have time to address it.