This is strange, because Confluence does have a ResizeProfileImagesUpgradeTask for performing this resize. It has existed for a very long time, as has the upgrade during upload process mentioned.
My guess is that for some customers this upgrade task failed at some stage in the distant past, but that in previous versions of Confluence we still declared the display size of images, and therefore scrunched the images appropriately.
We could probably fix this by increasing the number on the upgrade task, so that it runs again for everybody. It shouldn't cause any problems to run this task in later version.
In the meantime I suggest that if you hit this and it is causing a problem for you, ask support.atlassian.com for a patched version of ResizeProfileImagesUpgradeTask and instructions for running it.
Basically the steps are:
- Find your current buildNumber. It's in confluence.cfg.xml and the System Information page. I'll refer to it as "b" from now on.
- Alter ResizeProfileImagesUpgradeTask.java to return b+1 and recompile it. Put the class file in WEB-INF/classes/com/atlassian/confluence/upgrade
- Extract the default.properties file from the Confluence jar and set the version.number to b+2
- Either rewrite the default.properties file to the jar or put it in WEB-INF/classes/com/atlassian/confluence
- Restart Confluence
This should run the upgrade task and fix the images. Check the log for errors and report them to support.atlassian.com
Cheers,
Don
Hi mdavey@emich.edu
Thanks for taking the time to raise this issue. This has been on our backlog now for 6 years with very little movement in that time. Rather that leave this here I'm going to close the issue as won't fix, I believe that this better reflect its status.
If the issue is raised again in the future we'll readdress it
Regards
Steve Haffenden
Confluence Bugmaster
Atlassian