BuddyPress.org

Hi Jeff,

Right, that makes sense — it’s effectively coding the exception into the URL, get that.

Basically, what works:

* uploading an image that’s the correct size (regardless of format)

* uploading an image and getting as far as on-screen cropping

What doesn’t work:

* the cropped image is not getting written to the directory (jpg)

* editing avatar images is not properly updating the URL reference in the database (png)

(and then that breaks the avatar if people use the wrong image size)

I’ve just tested this by editing the avatar on one of our groups. png vs. jpg is not an issue. If it’s a size other than the correct size — i.e., if it brings up the cropping interface — it just doesn’t work. It crops the thumbnail, then the full-size image — both correctly. It just seems not to be actually writing out the file.

So, with the jpg, I get dumped to a page that says “The group avatar was successfully updated.” Except that the image hasn’t updated, and if I navigate to that directory, no jpgs whatsoever have been written. The URL is

http://noisepages.com/wp-content/blogs.dir/1/files/avatars/2/oscemote.jpg’%20is%20not%20an%20image.

— which is correct, oscemote.jpg in this case actually is not there. That seems especially odd to me, that even the uncropped jpg is apparently not getting uploaded to the directory.

With the png, I get dumped to a 404 error — it correctly creates both the full-size and thumbnail images on-screen, but at the last step I get a 404 on the group avatar editing page.

The png’s actually ARE in the directory. So I have what is apparently the full-sized image, plus the cropped one — oscemote-300×450.png

But the avatar itself isn’t actually changed in that place; the URL is still pointing at the JPG.