LonelyPilgrim

All right. So apparently the dynamic resizing is a part of WordPress.com but not part of the www.remarpro.com software — which does allow for dynamic resizing through the image_downsize filter. All of my “old” images that I thought were still being dynamically resized on the new blog were simply being scaled by the browser.

But the question still remains: Why won’t WordPress let me resize my “old” images? Shouldn’t it have some facility to do that — if nothing else, to insert a scaled img tag?

Okay, here’s the funny thing. For each of the images I’ve uploaded since my port to my own site, WordPress is making a set of resized images and leaving them in the upload directory. Here is my /wp-content/uploads/2014/10 directory:

cocker-150x150.jpeg
cocker.jpeg
joseph-a-shepherd-1931-150x150.jpg
joseph-a-shepherd-1931-236x300.jpg
joseph-a-shepherd-1931-513x288.jpg
joseph-a-shepherd-1931.jpg
prophet-amos-150x150.jpg
prophet-amos-244x300.jpg
prophet-amos-763x288.jpg
prophet-amos.jpg

And here I thought that WordPress did that resizing on the fly, hence the links to "sacredheart.jpg?w=199", for example. But in my new posts on my own WP site, it has stopped doing that. New image links are to the static images above, e.g. "joseph-a-shepherd-1931-236x300.jpg". Is something broken, or am I the one confused?

And the wp_postmeta table looks fine to me.

An update: On a whim this morning I queried the REST API with the URL www.lonelypilgrim.com — and it worked. But my site has never been www, just plain old lonelypilgrim.com without the subdomain. I never entered www as my URL anywhere, yet somehow the server has gotten the idea that this is my URL. It seems to me this may be something the Jetpack support people can fix, and I have asked them to.

Other Jetpack features are broken because of this, like Related Posts, and probably others.

I managed to get the follow button working by sending the blog ID instead of the URL as the data-blog attribute. But I would still like to know why the REST API is not recognizing my URL, and if possible, fix that.