-
Bug
-
Resolution: Won't Fix
-
Low
-
20
-
Minor
-
7
-
After migrating from on-premise to Cloud, large images doesn't render properly in pages on Cloud.
This image is too large to apply effects. Please make it smaller (less than 4,000,000px in total dimensions) and try again.
Workaround:
- Run below SQL on the on-premise to get all the pages in which there are large images which has effects enabled on them.
select spaces.spacename, parent_content.title AS "Page Title", content.title AS "Image Title", i.height, i.width, i.height * i.width AS "Pixels Size", ROUND(contentproperties.longval/1024/1024, 2) AS "file_size (MB)" from content inner join contentproperties on content.contentid = contentproperties.contentid inner join content parent_content on content.pageid = parent_content.contentid inner join spaces on content.spaceid = spaces.spaceid inner join bodycontent on content.pageid = bodycontent.contentid inner join imagedetails i on content.contentid = i.attachmentid where content.contenttype = 'ATTACHMENT' and contentproperties.propertyname = 'FILESIZE' and parent_content.content_status = 'current' and content.prevver is NULL and bodycontent.body like '%ac:image ac:queryparams="effects=%' and contentproperties.contentid in (select contentproperties.contentid from contentproperties where stringval like 'image%') and i.height * i.width >= 4000000 order by contentproperties.longval desc; - After the migration, go to Cloud instance, and open the page in edit mode, click on the broken image in edit mode and choose "Properties" then remove the effect (change it to none instead of having a border).
- is related to
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
[CONFCLOUD-65639] Images are broken and not displaying correctly on Cloud instance after migrating from on-premise
Hi,
We are actually during migration to the Cloud and we meet this problem. Please do not close this ticket, we still need your help with it. On our test instance it is some around 100 pages and it shouldn’t be done manually
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Hi there!
The actual impact of this issue should be very small. To enter the state described a user would have to have a 4,000,000px that has an image effect applied and then go through a migration. Additionally, it appears that there are not really any open customer cases, just one with vague reference to this CONFCLOUD and another completely different CONFCLOUD.
For any customers that do encounter this state, I would recommend using this query to find those very large images with an effect applied and remove the effect prior to migration. More details here: https://getsupport.atlassian.com/browse/MOVE-12613?focusedCommentId=23169426&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23169426
Best,
Ben