The new update should not give 501. The changeset is small. This update is to bump 4.4 and to add wrapper_tag option to allow other HTML tag besides DIV and wrapper_class option to allow other class name besides wp-pagenavi.
The rest of the code is untouch.
Also not too sure what does this has to do with the plugin? This plugin doesn’t even use the BJLL_AdminPage class name.
I am running the updated plugin on two of my sites without any problems.
If you can reproduce the problem let me know.
If you first activate lazy plugin (https://es.wordpress.org/plugins/bj-lazy-load/) and later… activate pagenavy you will find the error, so… to avoid that error I need to activate pagenavi first, and then activate lazy plugin.
I use PHP 7, maybe this is the tip 😉
I reproduce it:
http://prntscr.com/96x4k8
Thanks for respond.
You reproduce this on a fresh install with just bj-lazyload and just wp-pagenavi?
The plugin works fine with PHP 7, https://travis-ci.org/lesterchan/wp-pagenavi
No… sorry, only with my main site, I use this plugins:
Autoptimize
BJ Lazy Load
CDN Enabler
Disqus Comment System
GA Google Analytics
Postman SMTP
Query Strings Remover
VaultPress
Widget Logic
Wordfence Security (only anivirus scan)
WordPress Security Firewall (full options)
Wp Facebook Share Like Button
WP Social Sharing
WP-PageNavi
Yoast SEO
Broken Link Checker (deactivated)
WP-Optimize (deactivated)
Ad Inserter (deactivated)
I use serverpilot with my VPS, and cloudflare with dnssec, auto minify, rocket loader, standard cache, page rules for www-https, no apps, scrape shield for hotlinking, etc.
I use SSL security with strict in Cloudflare, that is all my configuration.
I use hueman theme.
I deactivate all plugins and only activate first lazy load and then pagenavi and the error still here.
May I try another plugin to lazy load with base64 image cript?, do you recomend me one?.
Thanks.
I am not sure, I don’t use much plugins as I will always code myself to be more efficient =)
To be honest, I don’t see why will it conflict. The two plugin functionality are totally different.
I will leave this open, see if other faces the same issue.
I had the same issue but fixed it by following Viktor’s suggestion above by activating PageNavi first.
The BJLL_AdminPage class extends scbAdminPage. The scbAdminPage class is used in both plugins, which could be causing the conflict.
