Tag Archives: beta

Autoptimize 2.2 coming your way, care to test?

So work on Autoptimize 2.2 is almost finished and I need your help testing this version before releasing (targeting May, but that depends on you!). The more people I have testing, the faster I might be able to push this thing out and there’s a lot to look forward to;

  • New option: enable/ disable AO for logged in users for all you pagebuilders out there
  • New minification/ caching system, significantly speeding up your site for non-cached pages (previously part of a power-up)
  • Switched to rel=preload + Filamentgroup’s loadCSS for CSS deferring
  • Additional support for HTTP/2 setups (no GUI, you might need to have a look at the API to see/ use all possibilities)
  • Important improvements to the logic of which JS/ CSS can be optimized (getPath function) increasing reliability of the aggregation process
  • Updated to a newer version of the CSS Minification component (albeit not the 3.x one, which seems a tad too fresh and which would require me to drop support for PHP 5.2 which will come but just not yet)
  • API: Lots of extra filters, making AO (even) more flexible.
  • Lots of bugfixes and smaller improvements (see GitHub commit log)

So if you want to help:

  1. Download the zip-file from Github
  2. Overwrite the contents of wp-content/plugins/autoptimize with the contents of autoptimize-master from the zip
  3. Test and if any bug (regression) create an issue in GitHub (if it doesn’t exist already).

Very much looking forward to your feedback!

Preparing (for) Autoptimize 2.0.3 or 2.1.0

It’s that time of the year again where I humbly ask Autoptimize’s users to download and test the “beta”-version of the upcoming release. I’m not entirely sure whether this should be 2.0.3 (a minor release) or 2.1.0 (a major one), but I’ll let you guys & girls decide, OK?

Anyway, the following changes are in said new release;

  • Autoptimize now adds a small menu to the admin-toolbar (can be disabled with a filter) that shows the cache size and provides the possibility to purge the cache. A big thanks to Pablo Custo for his hard work on this nice feature!
  • If the cache size becomes too big, a mail will be sent to the site admin (pass `false` to `autoptimize_filter_cachecheck_sendmail` filter to disable or pass alternative email to the `autoptimize_filter_cachecheck_mailto` filter)
  • An extra tab is shown (can be hidden with a filter) with information about my upcoming premium power-ups and other optimization tools- and services.
  • Misc. bugfixes & small improvements (see the commit-log on GitHub)

So, if you’re curious about Pablo’s beautiful menu or if you just want to help Autoptimize out, download the beta and provide me with your feedback. If all goes well, we’ll be able to push it (2.1.0?) out in the first half of August!

Heads up: Autoptimize minor release

Autoptimize 2.0 was a pretty successful release, if only because there were no major defects that forced me to quickly follow up with a bugfix release. That, off course, does not mean there were no issues at all or that no further improvements were possible. Hence Autoptimize 2.0.1 will be released within the next 2 weeks (or so), with the following changes:

  • Autoptimize now also tries to purge WP Engine cache when AO’s cache is cleared
  • Bail for AMP pages (which are pretty optimized anyway) to avoid issues with “inline & defer” and with AO adding attributes to link-tags that are not allowed in AMP HTML
  • Better support for renamed wp-content directories
  • Improvements to the page cache purging mechanism
  • Multiple fixes for late-injected CSS/ JS (changes in those files not being picked up, fonts or background images not beind CDN’ed, …)
  • Re-enable functionality to move non-aggregated JS  if “also aggregate inline JS” is active
  • Misc. other fixes & improvements, go read the commit-log on GitHub if you’re that curious

If you want to test this release out, you can download the beta from wordpress.org. Do ping me here if you think you’ve stumbled across a bug or simply to confirm all works just fine (esp. the WP Engine cache purge is a hard one to test for me, as I’m not hosted there)  :-)

Want to beta-test Autoptimize power-ups?

So I’m currently working on “power-ups” for Autoptimize, which I might commercialize later this year. Some examples of functionality I’m developing;

  • Excluding specific parts of your site from optimization (JS+CSS+HTML, JS-only or CSS-only), all from a simple configuration-screen
  • A settings-page to configure “above-the-fold”-CSS for specific pages
  • A power-up to speed up optimization itself (especially interesting if you don’t have a page caching plugin)

Drop me a line If you’re interested in beta-testing these power-ups, with a small description of where you would run this beta.

Wanted: testers for WP YouTube Lyte (the one with the new YT API)

As I wrote a couple of weeks ago, YouTube is shutting down their old v2 API, forcing WP YouTube Lyte to swith to v3. The main change; users will have to get an API key from Google and provide that in the Lyte settings page.

Initial development & testing has been done (this blog switched already) and I now need some brave souls to test this. You can download the “beta” from https://downloads.wordpress.org/plugin/wp-youtube-lyte.zip and report back here or on the wordpress.org support forum about how that did or did not work for you.

Looking forward to having to fix some nasty bugs until everything will finally be in it’s right place once again ;-)

Osunlade ft Erro Everything In Its Right Place

Watch this video on YouTube.