10 years after it became irrelevant (one of the first blogposts I wrote that generated discussions & traffic), Flash is now officially buried;
Quickie
blogposts op blog.futtta.be die -tegen mijn natuur in- snel-snel-snel de wereld ingestuurd zijn.
Fixed: WordPress 5.6 required Autoptimize settings change
PSA: WordPress 5.6 changes the filename of jQuery core. If you’re using Autoptimize and you have jQuery excluded (which is default) you will want to update your JS optimization exclusion list from js/jquery/jquery.js to js/jquery/jquery.min.js.
Update: Autoptimize 2.8 will automagically fix this, urgently looking for some testers to download https://github.com/futtta/autoptimize/archive/beta.zip (make sure 2.7.8 is disabled when enabling the beta). If all goes well and I get some confirmation the update (which has a lot more then just the fix) will go out today!
Update2: AO28 was released, all is (or should be) OK now 🙂
Question for you: what are Open Source’s values?
So open so(u)rcerers; what in your opinion are the core values you think are essential for the success of the open source ecosystem (be it WordPress or other)?
Autoptimize 2.7.7 fixes 2 security issues, please upgrade.
Autoptimize 2.7.7, which was release earlier today, has misc. improvements, but more importantly comes with 2 security fixes (one XSS, one malicious file upload, both for authenticated users), so please upgrade sooner rather then later.
Don’t take free & open source for granted; donate to Mozilla!
Do you ❤️ the free and open web and do you want to ensure a non-profit can continue to play an important role? Do you use Firefox or use MDN (Mozilla Developer Network) to check up on JS or CSS or HTML syntax?
We do too and as from today Optimizing Matters will donate $20 monthly. If you use Autoptimize or Async JavaScript or WP YouTube Lyte then please, pretty please, consider donating at https://donate.mozilla.org too.
Interview at WP Founders
I got interviewed at WP Founders; https://wpfounders.com/wordpress-plugin/frank-goossens-autoptimize/
Autoptimize code; blacklist/whitelist becoming blocklist/ allowlist
As of the soon-to-be-released Autoptimize 2.7.4, all occurrences of “blacklist” and “whitelist” in the code will be changed into “blocklist” and “allowlist”. There is no impact for users of Autoptimize, everything will work as before.
If however you are using Autoptimize’s API, there are two (to my knowledge rarely used) filters that are now deprecated and will be removed at a later stage. `autoptimize_filter_js_whitelist` and `autoptimize_filter_css_whitelist` still work in 2.7.4 but if you’re using them switch to `autoptimize_filter_js_allowlist` and `autoptimize_filter_css_allowlist` to avoid problems when they are removed in the release after 2.7.4.
Small post-publishing clarification dd. 22/07/2020: this post is just an announcement, I feel no urge to discuss the change and am not really interested in arguments pro or contra. Don’t fret over this change, fretting is useless, instead enjoy the summer, kiss your lover, read a good book, … 🙂
Autoptimize assets: 404-s nevermore?
So for those using AO who are seeing occasional 404’s on AO’d resources and (somewhat) into code; here’s a GitHub commit that might interest you;
https://github.com/futtta/autoptimize/commit/2e9d41d0d5bee9dd8069d86f3b1e269f799a5d50
(More later, gotta run now)
See you on wt.social?
Although I very much doubt this will ever be able to put a major dent in Facebook’s quasi-monopoly, I cannot but be supportive of Jimmy Wales/ Wikimedia’s new social network. If you want to join and appear in my friends-list there go to https://wt.social/u/frank-goossens.
Autoptimize closing in on W3 Total Cache
Fun fact; As per wordpress.org “popular plugins” ranking , Autoptimize is slowly but surely closing in on what used to be the go-to solution for Web Performance Optimization W3 Total Cache based on the “active installs” metric. Who would have thought? What a crazy ride …
