You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$bjll_options = new BJLL_Options();
$bjll = new BJLL( $bjll_options );
By default, this plugin is incomatible with SEO Ultimate plugin, as stated here for example. The simple and easy fix is to delete the second line. As far as I can tell, plugin works with it disabled just fine, and incompatibility with another plugin is resolved.
I also have a feature to request to be added. This new string of code here should be applied in order to strip "http:" and "https:" from src URLs, because in certain cirumstances (site with Cloudflare Flexible SSL + HTTPS Rewrites and no own server SSL) <nosript> src and data-src URLs aren't replaced, and on image load page turns into mixed SSL.
I'd suggest making it a checkbox option, or let users even choose – strip both HTTP and HTTPS, replace HTTP with HTTPS or do nothing. Or maybe you could automate it somehow, idk. Either way, the best practice now is to always use HTTPS, but not everyone may be using it still obviously.
The text was updated successfully, but these errors were encountered:
The issue might be addressed by wrapping the definition of bj_lazy_load() in a if ( ! function_exists(...) ) block to prevent it from being loaded more than once.
There are dedicated plugins like Really Simple SSL that can help with rewriting URLs to https, this is not a feature related to lazy loading.
In bj-lazy-load.php, there are these two lines:
By default, this plugin is incomatible with SEO Ultimate plugin, as stated here for example. The simple and easy fix is to delete the second line. As far as I can tell, plugin works with it disabled just fine, and incompatibility with another plugin is resolved.
I also have a feature to request to be added. This new string of code here should be applied in order to strip "
http:
" and "https:
" fromsrc
URLs, because in certain cirumstances (site with Cloudflare Flexible SSL + HTTPS Rewrites and no own server SSL)<nosript> src
anddata-src
URLs aren't replaced, and on image load page turns into mixed SSL.I'd suggest making it a checkbox option, or let users even choose – strip both HTTP and HTTPS, replace HTTP with HTTPS or do nothing. Or maybe you could automate it somehow, idk. Either way, the best practice now is to always use HTTPS, but not everyone may be using it still obviously.
The text was updated successfully, but these errors were encountered: