An error that appears in the error_log, although the plugin seems to work properly in the frontend:
PHP Fatal error: Uncaught Error: Call to a member function find() on bool in /home/hostinguser/public_html/domainfolder/wp-content/plugins/lazyload-background-images/admin/core/class-bg-image-processor.php:56
Stack trace:
#0 /home/hostinguser/public_html/domainfolder/wp-includes/class-wp-hook.php(324): PBLZBG_Image_Processor::process_bg(false)
#1 /home/hostinguser/public_html/domainfolder/wp-includes/plugin.php(205): WP_Hook->apply_filters('', Array)
#2 /home/hostinguser/public_html/domainfolder/wp-content/plugins/lazyload-background-images/admin/plugin-functions.php(21): apply_filters('pblzbg_buffer', '')
#3 [internal function]: PBLZBG_Init::{closure}('', 11)
#4 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/plesk/wp-cli-toolkit-command/toolkit-command.php(32): ob_end_clean()
#5 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/class-wp-cli.php(336): {closure}()
#6 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1409): WP_CLI::do_hook('after_wp_load in /home/hostinguser/public_html/domainfolder/wp-content/plugins/lazyload-background-images/admin/core/class-bg-image-processor.php on line 56
Simple custom theme, no builders, no other image related plugins. Background images are attached to html elements directly from theme php files using
style="background-image: url(...)"
]]>
Looks like the function is_preview_mode is conflicting with some other themes/plugins:
Uncaught Error: Call to a member function is_preview_mode() on null in /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/admin/plugin-functions.php:47
Stack trace:
#0 /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/admin/plugin-functions.php(18): pblzbg_is_builder_page()
#1 /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/init.php(37): require_once('...')
#2 /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/init.php(18): PBLZBG_Init::admin_init()
#3 /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/init.php(40): PBLZBG_Init->__construct()
#4 /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/lazyload-bg.php(22): require_once('...')
#5 /home/nginx/domains/domain.com/public/wp-settings.php(453): include_once('...')
#6 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1349): require('...')
#7 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1267): WP_CLI\Runner->load_wordpress()
#8 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#9 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process()
#10 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#11 phar:///usr/bin/wp/php/boot-phar.php(20): include('...')
#12 /usr/bin/wp(4): include('...')
#13 {main}
thrown in /home/nginx/domains/domain.com/public/wp-content/plugins/lazyload-background-images/admin/plugin-functions.php on line 47
Where we found a possible conflict:
themes/lemon-limes/includes/functions.php
plugins/elementor/core/base/elements-iteration-actions/assets.php
plugins/elementor/core/documents-manager.php
plugins/elementor/core/page-assets/loader.php
plugins/elementor/includes/managers/icons.php
plugins/elementor/includes/frontend.php
plugins/elementor/includes/preview.php
plugins/elementor/includes/maintenance-mode.php
plugins/elementor/includes/compatibility.php
plugins/elementor/includes/base/widget-base.php
plugins/optinmonster/OMAPI/Elementor.php
plugins/optinmonster/OMAPI/Elementor/Widget.php
plugins/wpforms-lite/src/Integrations/Elementor/Elementor.php
]]>
Hi,
This is plugin is a GREAT idea! I was really super excited to test it! However, as soon as I installed and activated the plugin, it triggers a fatal error on any page of the website.
FYI, I’m running Elementor. No caching plugin was active at the time of the testing.
]]>