deralict

6 of the 28 currently posted reviews are also complaining about lacking support. While I’m only speculating, I’ll bet they sought support because of similar issues to what I experienced.

Sorry to be harsh, but the choice to implement your product has been a major embarrassment for our company. I stand by my review…I say you don’t care because the dialogue accomplished in 3 weeks could have taken about 3 days, on more than one occasion I would wait 5 days for a reply. I ruled out Varnish as the culprit and demonstrated that to you, and had the host confirm that there’s nothing wrong with the server, and a competing plugin installed on another site on the same server works fine. The only conclusion remaining is that your plugin is incompatible with something else. While that is not unacceptable, dragging out your diagnosis over 3 weeks and taking days to answer is not worthy of a good review.

OK, I have figured it out. There was a server misconfiguration issue—the hosting company said that images were served by Nginx so they had to reconfigure it to bypass Nginx…or something like that. Not sure entirely. But I have confirmed that it does work.

HOWEVER, I noticed that the webp image that was now used instead of the source jpg image, was larger than the jpg image! I looked at all the webp images in the /uploads-webpc directory that had been converted, and noticed that while some of the smaller ones had been reduced is size when converted to webp, most of the files were larger in webp format.

I then did a test on one of the images that was larger in it’s webp format with an online converter. I compared the output of it to the webp version that your plugin created and to the original jpg file. It was 7% smaller than the original jpg, and 38% smaller than the webp created by your plugin.

Original image: https://fishinglodgesandresorts.com/wp-content/uploads/acc3-1.jpg

JPG: 225kB
Webp (your plugin): 327kB
Webp (online converter): 203.8kB

So even after getting the plugin to technically work, the conversion to webp does not actually make the site load faster (the opposite actually).

OK I changed that line, here is how htaccess looks now: https://www.dropbox.com/s/ukzt2y5pfc0j5in/Screenshot%202019-10-14%2014.25.11.png?dl=0

Still no work…

OK I created this rule (not sure if my syntax is correct) to taget a single image:
RewriteRule /wp-content/uploads/acc5-400×267.jpg https://fishinglodgesandresorts.com/wp-content/uploads-webpc/acc5-400×267.jpg.webp [T=image/webp]

Here is hwo htaccess looks now: https://www.dropbox.com/s/kutda7zfbxfmbt5/Screenshot%202019-10-14%2014.08.44.png?dl=0

Still doesn’t work…

I confirmed with the hosting provider that mod_rewrite is on and working properly. To verify I added a simple 302 redirect, and tested that it works (it does): https://www.dropbox.com/s/tifgu7s0lz1l2u7/new-htaccess.png?dl=0

Any other ideas?

OK I have emailed you a link to download the plugin files. One more thing perhaps worth mentioning: I am using Dynamic content to populate the Image Gallery widget (https://docs.elementor.com/article/310-dynamic-content). Would this have anything to do with the issue?

Well that’s good news (sort of). For the other images that are definitely not lazyloading, I’m using the Image Gallery Widget from Ultimate Addons for Elementor.

I thought the plugin would automatically work for images used in any Elementor widget. Is there anything that can be done to make this widget work with lazyloading?

Thanks for the reply.

1. I did read the FAQ…this is how I was able to determine that it was not working (according to the FAQ).

2. I’m not using a CDN.

3. I’m not using any other image optimization plugins.

4. Yes, all the webp files are in the /wp-content/uploads-webpc/ directory.

5. I went through all support threads before I started my own…that’s why I knew to include the screenshots I provided. I also verified the server has the required modules enabled.

6. The URL is https://fishinglodgesandresorts.com/lodge/aylmer-lake-lodge. It is not publicly available (still being developed) but I’m not sure what you mean by “add it to test environment”.

7. Here is a screenshot of the entire server config page: https://www.dropbox.com/s/oey17zo6ns20ket/entire-page.pdf?dl=0

8. .htaccess file content: https://www.dropbox.com/s/r7pk1jvb9upm6ik/htaccess.png?dl=0

9. Yes I confirmed with the hosting company those modules are enabled.

Yes, it looks like

Warning: Invalid argument supplied for foreach() in /wp-content/plugins/content-control/classes/Shortcodes.php on line 69

I’ve got this exact same error. I have the same plugin working fine on a site running WordPress 5.1.1, so that’s not the problem. The other site is not running WooCommerce which my site that has this problem does, so perhaps the plugin is not compatible with WooCommerce.

Also, the [content_control][/content_control] shortcode works fine, but the [content_control logged_out][/content_control] shortcode is the one that produces the error.

Thanks, Uptime Robot monitoring worked again after installing 5.115.1.

That fix worked great. Now if the Elementor folks could just build this into Elementor…

Hey that worked for me too! I’ve found that particles never got broken, but parallax did and this fixed it so both are working now. Cool!!

Doesn’t work for me either. It stopped working a while ago. I also can’t get it’s parallax script to work. I think that most of the scripts aren’t working in fact.