I had an interesting issue hit my site recently, that I still can’t figure out WHY it happened, but after a few days of troubleshooting, I have figured out what happened, and how to fix it.
First, let me say that my site runs on a Mac Mini running Mavericks (10.9.5). So, all of this MAY come down to some update Apple released recently, I’m really unsure. I also run my site behind Cloudflare, which I also was curious about. It seems to have cropped up on/around the time WordPress 4.2 was released, which is what I thought the issue was at first (and why I was involved in the wordpress.org forum thread here). The issue is basically that WordPress, in my case, wouldn’t generate thumbnails for JPG image uploads, but PNGs would. The issue cropped up right around the time that wordpress 4.2 was released, so the natual causation logic seemed to point to WordPress being the issue. Interestingly, it wasn’t. After banging my head on this for a while, a coworker finally found a note that WordPress defaults to using ImageMagick (imagick.so) for image processing if it’s present, otherwise it uses GD. So, I found a “plugin” that forces WordPress to use GD, and that fixed it. So crap, the issue is my ImageMagick install. The problem is, WordPress is failing silently, and not throwing ANY errors.
So, I added a simple script to test imagick using some code I found on php.net hoping it would actually throw an error. And it did throw an error:
PHP Fatal error: Uncaught exception 'ImagickException' with message 'Wrong JPEG library version: library is 70, caller expects 90
There we go. So, the issue is ImageMagick is being compiled against libjpeg version 9, but when it’s going to run, it’s being handed version 7. So, I was able to do an “mdfind” and see I had version 9 and 8 installed, as well as 7, both in /usr/local/lib, and with my PHP install. So, knowing I installed both 8 and 9, I removed 8 and 9, so only 7 was avaible, and then recompiled ImageMagick, and uninstall and reinstall imagick.so. Then, I ran my test, and it worked!
Being, obviously, a Fitbit fan, I picked up a Fitbit Aria a bit ago to track my (and the rest of my family’s) weight. I had been waiting patiently for them to update the Aria to support something a bit more modern than 802.11b, but sadly, that didn’t seem to be in the cards given their lack of response on the forums to requests for such functionality.
I recently picked up a Fitbit Zip at a Radioshack store closing for a heck of a good deal with the idea of giving it to my 2 year old son to see just how many steps his short legs make in a day. Obviously he didn’t need a One, or a wrist band style Fitbit, so the Zip seemed perfect. It still clips to clothing, and the battery reportedly lasts about 6 months (a CR2025, I believe), and best of all, it syncs over BLE (Bluetooth Low Energy). In the first few days I had the unit, it counted well over 8,000-10,000 steps a day (often beating both my wife and myself). The only issue I found was that it didn’t Sync quite as reliably as the Fitbit One. It seems that in order to get the 6 month battery life, they have the unit go into standby after a bit of inactivity. So during the night, when we’d remove the Fitbit from his clothes, it wouldn’t sync. I had to actually place the unit much closer to the receiver to get it to sync during the night (I’d just leave it on my desk which is where the receiver is). Other than that issue (which will come back) the unit is great. It’s small, does a good job, and we loved it.