http://www.mbpost.com/user-profile-imag ... 0/c-264341
When I try to visualize the parent page I can't.
I observed a similar thing for some photos for which the caption was too long. I was able to display them when I reduced it.
One of such pictures :
http://www.mbpost.com/after-the-race/287022/c-287001
Other bug (but I think distinct), photos with a size of 5Mpx do not appear correctly like this one :
http://www.mbpost.com/finisher/287108/c-264487
Eric

Thanks.
I'm not sure if there is not a difference between the two ways of posting a picture:
- first method the usual one with create page -> picture (on top)
- second method, add picture -> add new (left panel when on a page)

Matt, is there any news about this ? the third bug I mentioned is occuring quite often lately on MBPost, I don't see it on SP so perhaps there is a fix ?
Thanks !
Eric

visentin, an effort may be made this Fall for bugs on mbpost. We know there are some things that aren't quite right. I've got styling to do for mbpost as well.

Thanks.
Couple of examples of this bug :
http://www.mbpost.com/user-profile-image/288015
http://www.mbpost.com/beach-running/287869/c-284082

Wow! That's bad! Haven't seen a photo ever load like that.

Lots of tehm on MBPost. THese are only couple of examples.

Montana Matt wrote:The code on MBPost and SP is identical

By the way, taking you to the word ( ), there should be the GPX feature on MBPost. Well needed !

A few other features of Mbpost are missing too. I should make a MbPost tracker as well.

Montana Matt wrote:Yes, I'm not sure why it happens, but some information is not being inserted into the database when photos are uploaded. Thus on the photo page, the code isn't aware of all of the available sizes of photos and it displays the original when it should be displaying the medium resized image.

Talking about image sizes: in the new editor, inserting an image always generates the code for the medium sized version. That's almost always fine, except in those rare occasions where there isn't a medium sized version. I've seen that only a few times, when the original was already relatively small so there was never a need to reduce it to medium anymore.

Another minor point: when resizing an already inserted image in the new editor, from, for example, 500 pixels wide to 970, it would be nice if the medium sized image version would automatically be replaced by the original one if such a version exists. To put it more precisely, upon resizing, it would be nice if the new editor would automatically select the best version available for that new size. For big images this will help to solve the fuzziness, for small ones it improves the speed with which the page will load. Currently I do these adjustments afterwards in the HTML code - unless I forget.
As I said, this is just a minor issue, with a usable work-around, so you may want to spend your valuable time solving other issues. In fact, it seems to me that most people don't resize images, and consequently since the introduction of the new editor the vast majority of images in trip reports are simply the medium sized ones. Smaller ones, which were used frequently in the old editor, seem to have gone out of fashion quickly. I reckon that most people either don't realize they can resize, or just don't bother doing it. I can't say if the same is true for other page types, for while I take at least a quick look at most TR's, I don't do that for the other page types.

I agree that image inserting needs to be evaluated for the launch of SPV4. Basically more image sizes are needed than just medium. Same goes for the caption insertions, I'm seeing a lot of "taken on 05/27,2013" in photo captions of pages. This is because they are auto inserted from the image descriptions. Instead of inserting a original, I think a large could handle that just fine but the use of an original if a large does not exist (when the photo is barely 1000px in size).

The new editor takes more work for inserting photos, so I plan on doing some thinking on simplifying the process.

Montana Matt wrote:Yes, I'm not sure why it happens, but some information is not being inserted into the database when photos are uploaded. Thus on the photo page, the code isn't aware of all of the available sizes of photos and it displays the original when it should be displaying the medium resized image.

Diego found another clue regarding this bug: it happens only when you upload a picture as your profile pic. Not on normal pictures.

Good find! That should make replicating the issue a lot easier.

Why there is not a mbpost link in the SP main page now