Month: April 2015

Music from Our Tube: LA Priest – Oino

by

Heard “Oino” yesterday very, very early in the morning (around 6h20, while making my lunch-sandwiches, actually) on Studio Brussel and immediately loved the clickety clackety percussion-driven weird funk-like feel to it;

LA Priest - Oino (Official Video)
Watch this video on YouTube.

Did some web-digging and learned Samual Eastgate (aka Sam Dust), the guy behind LA Priest, was also in Late of the Pier, so guess I’ll have to go listen to them as well.

How to see WP YouTube Lyte’s cache for a post

by

WP YouTube Lyte stores data it fetched from YouTube’s API in WordPress’s add_post_meta, thus avoiding to have to contact YouTube for subsequent requests. You can clear the entire cache by ticking that option on Lyte’s settings-page, but maybe you want to only remove the cache for one specific post or even fix a problem with a stale cache-entry?
In that case, this little code-snippet (to be used in a plugin or in your child theme’s functions.php) might help:

if (is_admin()) {
    add_filter( 'is_protected_meta', 'lyte_unprotect_meta', 10, 3);
}
function lyte_unprotect_meta($protected, $meta_key, $meta_type) {
    if (strpos($meta_key,"_lyte_")===0){
        return false;
    } else {
        return $protected;
    }
}

This little filter tells WordPress not to consider post_meta with a key that starts with “_lyte_” as protected, rendering it visible in the “Custom Fields” box on the “Post Edit”-screen. If this is active you can just edit your post, going to “Custom Fields” and removing the entry (or change it’s value, if you’re a guncompressing, base64_decoding hard-ass like that);
lyte_cache_in_custom_field-compressor_smaller-compressor

Celebrating 300000 Autoptimize downloads with new release

by

300k-1, that isSo just now Autoptimize passed the 300000 downloads mark (6 months after reaching 200k), which feels huge to me. To celebrate I just pushed out version 1.9.3, which features -as becomes a minor release- small improvements and bugfixes. From the changelog;

  • improvement: more intelligent CDN-replacement logic, thanks Squazz for reporting and testing
  • improvement: allow strings (comments) to be excluded from HTML-optimization when comment removal is active (via API)
  • improvement: changed priority with which AO gets triggered by WordPress, solving JS not being aggregated when NextGen Galleries is active, with great help from msebald
  • improvement: extra JS exclude-strings: gist.github.com, text/html, text/template, wp-slimstat.min.js, _stq, nonce, post_id (the latter two were removed from the default “manual” exclude list on the settings-page and can be removed there if you want)
  • new in API: autoptimize_filter_html_exclude, autoptimize_filter_css_defer, autoptimize_filter_css_inline, autoptimize_filter_base_replace_cdn, autoptimize_filter_js_noptimize, autoptimize_filter_css_noptimize, autoptimize_filter_html_noptimize
  • bugfix: remove some PHP notices, as reported by dimitrov.adrian
  • bugfix: make sure HTML-optimalization does not gobble a space before a cite as proposed by ecdltf
  • bugfix: cleaning the cache did not work on non-default directories as encountered by NoahJ Champion
  • upgraded to yui compressor php port 2.4.8-4
  • added arabic translation, thanks to the ekleel team
  • tested with WordPress 4.2 beta 3 (yep, it works)

So there you have your present, no go unwrap it! Have fun! 🙂

Music from Monsieur Garnier: Acid Mondays

by

I still have some old Gilles Petersons “WorldWide” and Laurent Garniers “It is what it is” shows on my computer and once in a while I still “discover” gems in them. Just now, while on the train, I was listening to “It is what it is” Saison Quatre, emmission 2 and heard “El Recorrido” from Acid Mondays. The tracks starts out with just a (very) fat groove, but gets really interesting as from 2:37.

Acid Mondays - El Recorrido
Watch this video on YouTube.

Ain’t it funky now?

ALA about Angulars shortcoming: it’s the server, stupid!

by

In “Let links be links” at A List Apart Ross Penman discusses some of the dangers of building single-page-apps that entirely rely on client-side JavaScript (using e.g. AngularJS or Ember) and more importantly proposes a solution;

When dynamic web page content is rendered by a server, rendering code only has to be able to run on that one server. When it’s rendered on a client, the code now has to work with every client that could possibly visit the website. […] If framework developers could put in the effort (which, admittedly, seems large) to get apps running in Node just as they run in the browser, initial page rendering could be handled by the server, with all subsequent activity handled by the browser. […] If this effort could be made at the outset by a framework maintainer, then every developer using that framework could immediately transform an app that only worked on the latest web browsers into a progressively enhanced experience compatible with virtually any web client—past, present, or future. […]

WP YouTube Lyte 1.6.0: the one with the other API

by

I just released WP YouTube Lyte 1.6, featuring the following changes:

Proof the new player UI looks great;

Grizzly Bear - gun-shy [Official Music Video]
Watch this video on YouTube.

If you’re struggling to get a Google API key; there’s extensive information in the FAQ on the why, what & how. WP YouTube Lyte will automatically fall back to the old anonymous API v2 if you don’t provide a key. As API v2 will continue to work for a couple of more weeks, all will be fine. I am, in the mean time, working on a separate plugin that will automatically provide an API key for WP YouTube Lyte to use (and which in the future might offer other extra’s). You can contact me if you would be interested in test-driving that service-plugin.