Hi Dr Tester,
I highly doubt you’re still using the plugin since it was giving you trouble. However, if you still need help, let me know what WordPress HTTPS settings you have enabled and I can take a look at it for you.
Thanks,
Mike
ok, for now we fixed up the site without the plugin, but i’d me more than happy to help you get this plugin up to working for newest versions of wordpress.
There’s a lot of people looking for your plugin constantly
There are a lot of settings, how do i send you them all? a screen shot?
Well, the previous version that was released in December still worked with 3.2. However, last week I pushed out version 1.9 which added a few features and improved performance.
A screenshot will be fine if you don’t want to type it all out. 🙂
i’m first going to try your new plugin, i’ll let you know shortly
Thank you!
we’ll i’ve upgraded to the latest plugin and the site has slowed to a crawl,
Im not sure 100% , but i think there is progress over the last plugin, as now after quite a lapse the pages are loading,
This is my initial findings so far ( in 5 minutes of testing)
the only settings that are checked are
External HTTPS Elements
and
Force SSL exclusively
Hi Dr Tester,
I assumed that would be the case. That is the only option that would slow the site down, as the warning under the option suggests “Warning: This option checks that the external element can be loaded via HTTPS while the page is loading. Depending on the amount of external elements, this could affect the load times of your pages.”
The option beneath that “Bypass External Check” will stop the plugin from checking for the existence of the external elements over HTTPS when the page loads. However, any external element that can’t be loaded over HTTPS will be changed to HTTPS anyways, and that will cause it to not load at all.
I am currently looking into options for the plugin to “remember” which elements are safe to load over HTTPS and which aren’t so that the check isn’t done every time a page is loaded. That kind of opens another can of worms because then what if the external element is allowed over HTTPS after the plugin has remember that it can’t be?
Let me know how that works for you. Also, a link to the site would be nice so I can see how many external elements are being loaded on the page. Maybe we can do some optimization.
Thanks,
Mike
ok,
Thank you for your help and advice,
Whilst not absolutely crucial for our site currently, as we already bypassed the problem by creating our own plugin solution, your plugin goes a further and is far superior.
Currently, i have turned off our plugin and installed yours
site is
http://www.yofr.org/
donation page (https) is https://www.yofr.org/donation/campaigns/?camp=3
Once you have finished looking, if you are able to make some simple suggestions i would be happy to try those, but otherwise, i would like to deactivate the plugin and reactivate ours (as it is a live site)
Did you try the “Bypass External Check” option? That should stop it from slowing down.
awesome! looks like there was instant improvement there!
It looks like the only thing not loading on that page is this script:
https://lite.piclens.com/current/piclens_optimized.js
If that’s okay, you should be set.
I really can’t see why it’s taking so long to check the external elements for HTTPS availability. I’ll look into some alternative methods.
Let me know if you have anymore questions.
Thanks,
Mike
does that mean piclens would not work on the entire site, or just the HTTPS required pages?
If its the https pages, then yes thats fine, but if it would stop it from working on the entire site, it would be a problem
Yes, just the HTTPS pages.
ok, then that should be fine
the speed looks ok now
