niw2cp

I moved to another host. I worked with HG to resolve the issue, but neither of us could figure it out. I suspect there is an issue with the multiple image upload to AWS.

Only image mime types get broken into smaller versions (thumb, medium, etc), so setting to another mime type bypassed WordPress’s image resizing process. Viola, a single image file successfully uploads to S3, but with two problems.

The image on S3 is now only at the original filesize with no smaller versions. And, the admin area will show filetype icons instead of the image thumbnail. ??

I lost the trail at the SSL version for cURL. (See my issue at Github. https://github.com/bradt/wp-tantan-s3/issues/64) Do you have a VPS with HG? You may be able to control things like that.

Matt, have you verified the custom image sizes are actually being created and stored locally?

I suspect a server configuration issue. With whom is your WordPress install hosted?

This appears to be controlled by WordPress mime type.
Since jpgs and pngs are set to the image mime type. If you change them to the application mime type, the images begin to upload to S3.

I’ll submit a code suggestion to github.

Yup, did all that. Then the worst thing happened. I woke up the next day and it was working. I have no idea what I did. All the things I tried didn’t appear to work at the time. They included:

Resetting the .htaccess file. (Once I even got a blank page with an error that saying it couldn’t find /site-map/ Huh?)

Cleared all redirects from Redirection plugin. (No apparent effect, which pissed me off cause that was my biggest suspect.)

Cleared the database cell for option_id=12188 rewrite_rules. (No apparent effect. Replaced data as it was.)

I don’t think I’ll be upgrading this particular blog to 3.2.1 for a while. At least, until I have a week to retrace my steps and find out what happened and why there was a delay.

And I didn’t mention it before, but the page it was defaulting to was set to a site-map template. So at least the visitors got to see some content rather than a blank page.

That’s the problem. The “Front Page displays” is set to posts, not a page.