Cyberchicken

The “uploads” foldername is available in a variable, I believe it’s easy to embed it in the regex and make it more portable.

Better. But I understand that opacity problems are due to the underlying animate.css library.

You changed the block’s icon, I appreciate that.

Thank you

I suspect the problem would go away using the updated version of animate.css
Because there is an ancillary library for triggering animations:
https://animate-dynamic.ga/

Seemed reasonable but it doesn’t work:

first the precedence of the selector should be higher, like
.wp-block-ab-animate.ab-end { opacity: 1 }

second, the opacity is not transitioned, so the block just appears out of nowhere at the end of the animation.

Looking forward for the next iteration.

BTW you could add a “reset” option in the scroll detection library.

Thank you

Yes, it worked! Thank you!

I suggest the two developers to have a talk.

https://chrome.google.com/webstore/detail/i-dont-care-about-cookies/fihnjjcciajhdojfnbdddfaoknhalnja?hl=en

I’ll try to drop a line to the other guy.

Update:

I then stripped all the root part of the path, leaving just
“wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff”
and it worked.

I was wrong: it worked just for the root fo the site; for anything with a non-blank slug the fonts that were tried to be loaded from a path like
https://www.example.com/home/h6kj08g4/public_html/myWonderfulPageSlug/wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff

So I decided to uninstall Kirki plugin, delete the correponding option from the db, reinstall the plugin, and now everything works as it should.

Note: the option kirki_downloaded_font_files is much leaner, (I believe there were many duplicates before).
All the local paths are like
“/var/www/vhosts/example.com/httpdocs/myWordpressInstallationFolder/wp-content/fonts/questrial/QdVUSTchPBm7nuUeVf70sSFjuW44JUcz.woff”
which I think is wrong, because the document root could change, and should be calculated, not hardcoded in the db; the cache should take care of any performance hit.

Please make me you considerations.

Thank you

Ok!
If I one day will find the time, I will submit an extention to the plugin.
For the time being it will be ok just to know its boundaries.
Thank you!

I can’t chek right now, but php is certainly be 7.3 or 7.4 and auto updates are ON for core themes and plugins.
I’m sorry, I did the mistake not to note those things, but that error broke many different sites I manage, so I was a bit busy.
I’ll try to reconstruct some info.

There was a typo!

/**
 * Plugin Name: InnerspaceZeta Customizations disable some useless email notifications
 * Plugin URI:
 * Description: 2021
 * Author: InnerspaceZeta + VS49 + UnDinosauro
 */

// https://developer.www.ads-software.com/plugins/plugin-basics/header-requirements/

//require_once WPMU_PLUGIN_DIR.'/includes/debuglibZ.php';
//isz_log("innerspaceZeta mu plugin loaded");

// call_user_func(function (){ // prevents polluting the global namespace
// });

function iszDontNotifySuccessfulUpdates( $send, $type, $core_update, $result ) {
	if ( ! empty( $type ) && $type == 'success' ) {
		return false;
	}
	return true;
}

add_filter( 'auto_core_update_send_email',   'iszDontNotifySuccessfulUpdates', 10, 4 );
// add_filter( 'auto_plugin_update_send_email', '__return_false' );
// add_filter( 'auto_theme_update_send_email', '__return_false' );
add_filter( 'auto_plugin_update_send_email', 'iszDontNotifySuccessfulUpdates', 10, 4 );

>I don’t think you’re right.

I don’t either. But I am baffled: this plugin has always been very good, and also the team at UpdraftBackup is very good at communicating, fixing and developing. So I really have a hard time explaining why two goods make one (slightly) worse.

>There are other plugins that turn off email notifications, like this one https://www.ads-software.com/plugins/companion-auto-update/ and it’s doing a better job.

Apart from the notifications debacle I think I have no complaints, so I went for the self written mu-plugin.
I paste it here since it’s so small:

/**
 * Plugin Name: InnerspaceZeta Customizations disable some useless email notifications
 * Plugin URI:
 * Description: 2021
 * Author: InnerspaceZeta + VS49 + UnDinosauro
 */
function wpb_stop_update_emails( $send, $type, $core_update, $result ) {
	if ( ! empty( $type ) && $type == 'success' ) {
		return false;
	}
	return true;
}
add_filter( 'auto_core_update_send_email',   'wpb_stop_auto_update_emails', 10, 4 );
add_filter( 'auto_plugin_update_send_email', 'wpb_stop_auto_update_emails', 10, 4 );
add_filter( 'auto_theme_update_send_email',  'wpb_stop_auto_update_emails', 10, 4 );

It’s been working fine for a week now in a no-traffic site but consider it untested.
I took the code mainly from here

Superficially this is crazy. I mean it’s just a simple filter wrapping!
But then I try to think a bit more conspiracistly: the notification where arbitrarly turned on with wp 5.5 (if I remember right), so maybe it was wpcore devs themselves that asked the plugin devs not to subvert this thing, maybe for “security” reasons, maybe in the waiting for a proper solution (that never came). A big stretch and a long shot, I know.

Anyway I’ve had enough to add filters in my mail clients, I think I’m rolling out a mu-plugin on the lines (actually 3 lines literally) of this article.

Gee Danstano, I can’t remember what site I was working on that had to use this plugin.
Sorry, I’ll write back if I recall what I did.

Additionaly, the replacement didn’t take place.

Just to confirm, as per your post, the calc function spaces are being removed when using CSS minifier: Minify (default), but if you switch to CSS Tidy the spaces are not removed?

Yes!

If I remember right: if you want to keep quality=92 just save 91, then save 92 again and the button stays active.
Yes it’s a trick, per the UI shouldn’t be needed, but I totally understand the need to protect the web service from whack-a-mole on the RESMUSH EVERYTHING button.