So they added a new WYSIWYG editor in WordPress own app for iOS. And to my Initial amazement it looks like it handles images the correct way by first uploading them, and then gives you the different automatically created sizes done by the server. Maybe I’m finally able to upload images and have Retina support without having to use my Editorial workflow? But when looking at the generated HTML, the height and width of the images is set to zero. It points the URL to the full resolution image, even if you select a smaller one. Not good. If you save a draft, it forgets your image settings like alignment and title.
I’m working on my script for uploading images directly from the iOS Markdown text editor app Editorial to WordPress. The current script uses xmlrpc-Wordpress library, but I’m writing my own so the user doesn’t have to install the extra library just to use my script.
When uploading files with xmlrpclib, I got this annoying thing happening. Every time I uploaded an image using xmlrpclib and the function wp.uploadFile the uploaded file got wpid- prepended to the filename of all my uploaded files.
Using Marsedit 3
I’ve been dabbling around with different blog editors for Mac now for a while, trying to find one that suits my needs. I usually try to do most of my blogging on my iPad, but when writing on my Mac I’ve used Byword in combination with Marked2 to do the initial texts written in Markdown.
There are several JPEG image compression tools available that takes a jpeg file and reduces the size of the photo without altering the quality. But which one works best for posting images on a website? I was curious, so I took the tools I usually use and put them through the compress photo function. All applications tested claims not to lower the quality of the image. I’m concentrating on testing jpeg files here, and do a followup article later with results for optimizing PNG files.
hAtom errors and Google PageRank
When I checked my blog in Google Webmaster I noticed a lot of errors in the Structured Data section. After fixing the errors in WordPress by adding structured data, my traffic increased without any changes. That includes posts. So obviously Google uses hAtom when setting PageRank.