-
Bug
-
Resolution: Fixed
-
Medium
-
2.8
-
None
Space Logos are currently stored in the home directory and accessed throughout Confluence using the ResourceManager. The ResourceManager is not widely used and therefore causes various problems to occur around Space Logos. If we changed the Space Logo to be stored as an attachment to the Space Description, we could avoid these bugs, and deprecate the ResourceManager.
This storage/display mechanism would mirror that used for User Icons, simplifying the system as a whole.
- causes
-
CONFSERVER-8637 Resin 3 responses are being concatenated sometimes when a custom logo is specified
- Closed
-
CONFSERVER-11325 Refreshing a page hangs and corrupts page results when a custom logo is used on Confluence running behind mod_jk or mod_proxy_ajp
- Closed
-
CONFSERVER-8908 Space/global icon doesn't work in a cluster
- Closed
-
CONFSERVER-12419 Global Logo in new spaces causes FileNotFoundException
- Closed
-
CONFSERVER-15175 CLONE -Unable to change space logo
- Closed
-
CONFSERVER-5860 Unable to change space logo
- Closed
-
CONFSERVER-11338 Custom global logo image height is not respected
- Closed
- is related to
-
CONFSERVER-11994 Race condition in HiLoIdRepairUpgradeTask and ResetHiLoAfterImportListener can lead to primary key violations in upgrade tasks
- Closed
-
CONFSERVER-11424 Regression : Global (or Space) Logo is scaled
- Closed
-
CONFSERVER-11590 Space logo is not restored on import
- Closed
- relates to
-
CONFSERVER-16509 Upgrading from any version before 2.9 to 3.0 doesn't migrate attachments and/or breaks custom space logos
- Closed