symisz

Thanks for the reply. I’ve figured it out what was causing my error and it was my own wrong doing; there where some cached files that got mixed up with a new installation. Once I purged it, the error was gone.

my guess is that the Gutenberg plugin is now part of the core, however does this mean the latest updates are align or ahead of this plugin?

well, if you got any pointers on how i can get the charset and allocation to prefill. that would be great.

i’ve to correct myself here. i was able to prefill just the host, not the charset and allocation.

i’ve been using duplicator on autopilot, somehow missed seeing these options. cheers!

Hello @corylamleorg,

Yes, I do know which settings I need.
I was just wondering if I could change the default settings that are autofilled, so I could autofill to my desired settings.

Thank you for this plugin!

• This reply was modified 4 years, 9 months ago by symisz.

beware the single quotation marks are modified within this text field, so i left them out here below:

/(elementor-background-overlay)/m

• This reply was modified 4 years, 9 months ago by symisz.
• This reply was modified 4 years, 9 months ago by symisz.

because there is no response from the plugin author, i’m adding the solution for anyone interested in using this.

modify the plugin php file: class-lazy-load-elementor-background-images-public.php
add the following line to the function “public function elementor_frontend_the_content”:
‘/(elementor-background-overlay)/m’,

it will look something like this:

public function elementor_frontend_the_content( $content ) {
// NEW 2020-02-08 … now lazyloads column backgrounds!!! feedback welcome!!!
// NEW 2020-03-13 … now lazyloads Swiper and Flip Box widget backgrounds from Elementor Pro
return preg_replace( [
‘/(\selementor-section\s)/m’,
‘/(elementor-column-wrap)/m’,
‘/(elementor-flip-box__front)/m’,
‘/(elementor-flip-box__back)/m’,
‘/(swiper-slide-bg)/m’,
‘/(elementor-background-overlay)/m’,
], ‘ $1 lazyelementorbackgroundimages ‘, $content );
}

}

• This reply was modified 4 years, 9 months ago by symisz.

@giuse that was fast and it worked nicely! thank you!

i should mention that people should clear their cache as well: wp cli cache clear
as i still got the plugin message before the cache clearance.

• This reply was modified 4 years, 10 months ago by symisz.

Thanks for getting back to me @giuse

Here is the screenshot of my terminal:
https://ibb.co/0XQkWG0

I use WP CLI to operate WordPress throught the command line.
And your plugin message popups in there, might be not intended.

However being able to operate your plugin through the command line would be an awesome feature!

• This reply was modified 4 years, 10 months ago by symisz.

@avpman

This is a bug introduced in the most recent WordPress update.

The error also exist in WordPress 4.
@entik I had an issue with sessions still being active after logging out, since I can’t reproduce the error, it seems like a non-issue now.

the option in Cerber to disable wp-login.php creates this conflict, as the default WordPress logout links to wp-login.php. this error leaves the login session open after trying to logout. simply remove the wp-login.php in your address bar (https://mysite.com/portal/?loggedout=true) will successfully terminate your login session however.

I should have read “the fine print” on: https://wp-puzzle.com/our-support/
that you don’t provide support to collisions with themes.

• This reply was modified 6 years ago by symisz.