I don't know why this happens, but I do know how to avoid it -- at least as far as embedded images are concerned.
The root issue happens because Ning, for whatever reason, likes to append width properties to image URLs when you upload images to the site. You can see this very easily by clicking the "Edit" button on any build you've created, then clicking the HTML Editor tab to view/edit the build markup. Locate any image (CTRL+F "img src") and you should see something like this (taken from the Crimson Scar's perk spread, which is currently being affected by this bug, and I haven't bothered fixing as I've been meaning to make a new perk spread anyways):
<img src="discussions/19001-20000/19446-CSPerks.png?width=750" width="750" class="align-center" />
Note how, at the end of the image URL, there's that ?width=750 bit? Go ahead and just delete it. It's redundant anyways; you've got the width="750" element doing that already. It's the ?width=750 suffix that causes this bug. I don't know why, but there you go. Here's what the image looks like with that width suffix still in the URL:
And here's what it looks like when I remove the suffix:
I don't know why this happens, but I do know how to avoid it -- at least as far as embedded images are concerned.
The root issue happens because Ning, for whatever reason, likes to append width properties to image URLs when you upload images to the site. You can see this very easily by clicking the "Edit" button on any build you've created, then clicking the HTML Editor tab to view/edit the build markup. Locate any image (CTRL+F "img src") and you should see something like this (taken from the Crimson Scar's perk spread, which is currently being affected by this bug, and I haven't bothered fixing as I've been meaning to make a new perk spread anyways):
<img src="discussions/19001-20000/19446-CSPerks.png?width=750" width="750" class="align-center" />
Note how, at the end of the image URL, there's that ?width=750 bit? Go ahead and just delete it. It's redundant anyways; you've got the width="750" element doing that already. It's the ?width=750 suffix that causes this bug. I don't know why, but there you go. Here's what the image looks like with that width suffix still in the URL:
And here's what it looks like when I remove the suffix: