25 Feb 2017


1. I might have known about this since 2012, but I was reminded about it again today.

When I go to my WordPress Dashboard > Thesis > Skin Design > Layout & Dimensions, it says the content width is 617 pixels. I was just starting to write consistently this year. And I forgot what the width of my image should be. So I was basing the width of the images I upload based on the content width of 617 pixels.

After implementing KeyCDN, I right click and open an image in a new tab every now and then to see if it is being served through my CDN. Today, I just noticed that the image opened in a new tab is slightly bigger than the image in my post. That’s when I was reminded that I was uploading resized images with a width of 617 pixels. But WordPress automatically resizes all of my images on my posts to 565 pixels.

The reason why my images maxes out with a width of 565 pixels, and not 617 pixels on posts, is because the difference of 52 pixels was for paddings, borders, and margins. Even the paragraphs on my posts and pages maxes out with a width of 565 pixels because of paddings, borders, and margins.

Going forward, I will resize all of my images with a width of 565 pixels, not 617 pixels, before uploading them to my website. I won’t be editing and resizing my previous images anymore because it takes a lot of unnecessary work.

Maybe when I’m not lazy I’ll resize and optimize my previous uploads. The image at the start of this post is already using the correct width of 565 pixels.

2. Jetpack said that starting with Jetpack version 4.6, their plugin is already compatible with PHP 7.1. But I just changed my PHP version from 7.0.16 to 7.1.2 to check if it really is compatible already. It’s not. PHP 7.1.2 is totally not compatible yet with Jetpack 4.6.

That’s why I’ll stick with PHP 7.0.16 for now. And I’m sure that PHP 7.1.2 is also not compatible with other parts of my website as well.

PHP 7.0.16 was released last 16 Feb 2017.

PHP 7.1.2 was released last 17 Feb 2017.

Next post:

Previous post: