Vor drei Tagen ist die neue WordPress Version erschienen.
New features in 4.6 help you to focus on the important things while feeling more at home.
Hm, na dann… :-)
In den paar Installationen, die ich schon aktualisiert habe, lief alles glatt und ohne Auffälligkeiten, daher drücke ich nun auch hier in der Bloghütte den Update Button.
Years ago I found an old Reußenzehn cabinet with two 12" speakers in an old rehearsal room that we cleaned up. Since neither the speakers nor the cabinet beared any markings regarding impedance and wattage, I was reluctant to use this box, and so it kind of hybernated for quite some time now.
In the last weeks I worked on two tube amps, changing power tubes, setting the bias, and one transistor amp, where I repaired a blown power section. So it turned out that I have a need for a relatively small and compact cabinet to test ...
Gestern abend ist eine neue Version mit Sicherheits- und Wartungsfixes erschienen. Bei den diversen Installationen, in die ich involviert bin, hat sich das automatisch aktualisiert, auch bei älteren Versionen als 4.5.2, wie gehabt gibt es die Source aber auch zum Download auf wordpress.org.
WordPress versions 4.5.2 and earlier are affected by several security issues: redirect bypass in the customizer, reported by Yassine Aboukir; two different XSS problems via attachment names, reported by Jouko Pynnönen and Divyesh Prajapati; revision history information disclosure, reported independently by John Blackbourn from the WordPress security
For a long time it has bugged me that the css for the recent version of my site was desktop-down. I made some adjustments for adaptive/responsive behaviour three or four years ago, but since the code base of my site is organically growing since I started it on WordPress in 2005… uhm, I think you get the picture. So all I did back then was to consider how the site should look on smaller screens, and making modifications inside max-width media queries, keeping all of the desktop-related stuff as the default styles, outside any media queries.
Of course when starting ...
Motivated by the sudden appearance of the "Add to home screen" prompt, I spent the last couple of hours to tune my Service Worker / caching behaviour:
- I can now exclude parts of my site from the service worker. This was an important feature for me, since the WordPress backend didn't sit too well with stubborn cached items.
- I established a number of caches for different items:
-- a "static" cache that has the base css and the page that gets displayed when the network is offline.
-- a "content" cache, that stores up to 25 URLs a visitor has, well, visited, while being online.
-- an "image" cache, that stores up to 45 image files, and finally
-- an "asset" cache for up to 35 files (everything that is not HTML and not an image).
The limits are rather random, but I think each cache has an build-in maximum of 50 entries (?), so to see if it works, I choosed numbers smaller than that.
Ha! It! Really! Works!
I have to admit I was a bit sceptical of the outcome after I tweaked and added things and bits of my website at the Indiewebcamp in Nuremberg, setting up a service worker and offline caching things, adding a manifest file … while in theory I understand what all of this was supposed to do, I felt a bit dumb for not completly grasping how to control the stuff.
So as so often when learning new tricks on the web, it started with copy/pasting a working solution and trying to adapt this to my ideas.
Dear js gurus in my timeline, is this the correct way to exclude urls from the power of ServiceWorkers?