An important component of responsive design is handling images. Forcing mobile visitors download of full sized images isn’t optimal, neither is serving up blurry low-res images. On top of that if visitors are viewing on higher density displays then it’s all blurry.
Sometimes you have a set of custom posts that are subscriber only. Sometimes you want a couple posts to be available publicly. Unfortunately there’s not a well documented way to do this, and the last thread on the topic received the response “there isn’t that yet.”
Rough day for the internet. A vulnerability was found in the OpenSSL cryptographic library, commonly used to secure Apache and nginx servers. This affects roughly 70% – 80% of servers currently in use. From the Heartbleed Bug site:
The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.
You can test if your server is vulnerable at Qualys® SSL Labs.
A list of potentially affected sites (that you may consider changing your password on) can be viewed at Digital Trends.
Additional list of potentially affected sites can be viewed on Mashable.
After migrating my site earlier this year I scanned through the old files to verify that everything made it across. During this verification I kept seeing dot files that weren’t a part of WordPress, and that set off some alarms. Turns out that the old site had been piggy backed for some nefarious (or at least unintended) purposes.
I’ve run into several IE quirks in my time, but this is the first stumper I’ve had since IE8. The symptom was content not appearing below the header, but styles and content above that were loading fine. In addition this error did not show up on local test environments, even when emulating the same version of IE (9). On top of that some computers the client was using worked fine, while others did not.