Bug #21849
closedImages not rendering correctly
Added by Laurie Hurson 9 days ago. Updated 5 days ago.
0%
Description
From a user:
"where after working fine for a while (including after the migration), a series of glitches seems to have snuck in. A couple of images are not rendering, and emojis in headers have been replaced with ‘?’.
I tried seeing if the revisions panel would allow me to recover an older version, but I’m wary of that creating other missing sections. Would it be possible to take a look at what might be going on? No change we made on our end could lead to these things breaking as the last edit we made was a while ago.
Here’s the link - https://citevision.commons.gc.cuny.edu"
I have also had issues with images on https://testworkshop1.commons.gc.cuny.edu/'
they render on front end but when you go to edit the page, they throw an s3 error.
Files
| image.png (97.8 KB) image.png | Laurie Hurson, 2025-01-24 09:55 AM | ||
| Screenshot 2025-01-27 161750.jpg (61.1 KB) Screenshot 2025-01-27 161750.jpg | Marilyn Weber, 2025-01-27 04:18 PM | ||
| Screenshot_2025-01-27_17-35-58.png (128 KB) Screenshot_2025-01-27_17-35-58.png | Chrome | Boone Gorges, 2025-01-27 06:37 PM |
Updated by Boone Gorges 9 days ago
- Category name set to S3 Uploads
- Status changed from New to Reporter Feedback
- Assignee set to Boone Gorges
- Target version set to 2.5.1
I don't really have enough details to reproduce exactly what the user's reporting. But I did notice that some images were not appearing correctly, for example the nice images on the homepage: https://citevision.commons.gc.cuny.edu/ I did a bit of investigation, and it appears that something got missed during the post-migration work: I had a script that set public-read permissions on S3 assets belonging to existing public sites, but that script only handled sites that were created before the Dec 2024 snapshot. So it missed this site, which was created on 2025-01-13. I just updated those S3 ACL rules manually for the site, and the images are now appearing on the homepage. (I'm currently running the script for all sites created after the Dec 2024 snapshot, which will take another 15-20 minutes to finish.)
If the user is still experiencing problems, please have them formulate them like this: I am looking at (clicking on, editing a post on, whatever appropriate verb) URL X, I expect to see Y, instead I see Z.
Updated by Boone Gorges 9 days ago
Sorry, I forgot to mention that the emoji issue is separate, and is already documented in #21820. In the next couple days, I'll be running a tool that attempts to fix this problem across all sites. In the meantime, please don't attempt to fix the problem by reverting to a previous revision - it won't work, because the emoji are broken there too. If you don't want to wait for my repair tool, then you can manually modify your posts to restore the emoji (my repair script will skip any posts that have been modified since the migration).
Updated by Marilyn Weber 6 days ago
I think this is related.
Angela LaScala-Gruenewald writes
I am a fellow at the Teaching and Learning Center and helping out with some web design in 2024-25. I know you did a migration last week and I noticed after that all the images on the back end (Block Editor) of the site I'm working on (https://testworkshop1.commons.gc.cuny.edu/) just showed alt text. I've included two images below: first of the front end (which looks good!) and one of the back end in Block Editor where one of the alt. text error messages is circled in red. I was wondering if you had a fix for this? I spoke with other TLC staff who have noticed the same issue on the sites they are working with.
Updated by Laurie Hurson 6 days ago
I think this may also be related.
The site here is supposed to have a video: https://hafiqwis000.commons.gc.cuny.edu/elevator-pitch/
Where the video is the error says:"No video with supported format and MIME type found."
The user reports that they do not know what this used to be but CSS indicates the page has a video block that should be pulling a .mov file from the media library. The video link is:
I was able to upload a .mov file and play it on the commons here, so I think this may have something to do with the migration and changes to the media library URLS?
Updated by Boone Gorges 6 days ago
first of the front end (which looks good!) and one of the back end in Block Editor where one of the alt. text error messages is circled in red.
I needed to add a signed-S3-URL filter for raw post content from the REST API. I've done so in https://github.com/cuny-academic-commons/cac/commit/9b3f5fc3d54f6efa9b58b9a72ab5c5975c40a073 and it appears to have solved this problem.
Updated by Boone Gorges 6 days ago
The site here is supposed to have a video: https://hafiqwis000.commons.gc.cuny.edu/elevator-pitch/
Where the video is the error says:"No video with supported format and MIME type found."
In Chrome, I'm seeing a player, and when I press Play I hear the audio. See attached screenshot. I see the error notice when I view in Firefox.
I don't think this has anything to do with S3 or with our migration. It appears that the video may have been encoded with a codec that doesn't have very good browser support: https://caniuse.com/hevc See also https://core.trac.wordpress.org/ticket/42775. I don't have a Safari browser within arm's reach, but if the user's embed works properly in Safari, then it indicates that this is an issue specific to this video. In that case, my suggestion is to reencode the video using a tool like Handbrake https://handbrake.fr/downloads.php
Updated by Laurie Hurson 5 days ago
Boone Gorges wrote in #note-6:
I don't think this has anything to do with S3 or with our migration. It appears that the video may have been encoded with a codec that doesn't have very good browser support: https://caniuse.com/hevc See also https://core.trac.wordpress.org/ticket/42775. I don't have a Safari browser within arm's reach, but if the user's embed works properly in Safari, then it indicates that this is an issue specific to this video. In that case, my suggestion is to reencode the video using a tool like Handbrake https://handbrake.fr/downloads.php
Thanks for looking into this Boone and apologies for the over reporting. I will let the user know.
Updated by Boone Gorges 5 days ago
Not over reporting! I'd rather have too much info than too little. It just turns out that it's not related to S3 or Reclaim or the current ticket.
Updated by Boone Gorges 5 days ago
- Status changed from Reporter Feedback to Resolved
I believe that the specific issues raised in this ticket have been resolved. If the particular reporters write back with more issues, please feel free to post it here. Otherwise, if you get other reports of images or other uploaded assets not working as expected, please provide details in a separate ticket so that I can triage.