Recently we noticed that Cloudinary.com cropped images within a card component in our app stopped displaying. We used the res.cloudinary.com code to auto focus on the headshot faces so that we did not have to manually crop our images to a square shape to capture the centered faces.
If we set the image field data back to point to just the uploaded images in Glide it will show but now the image references imagekit.io instead of previously being listed as Cloudinary.
Is there a reason that the cropped Cloudinary URL now does not show the image in a Card component? This is a PAID Business 2023 Plan so the removal of Cloudinary from the FREE plans does not factor in here.
Can anyone provide guidance on this? It just began happening 4-5 days ago. Did Glide decide to remove Cloudinary from all of it’s images and transition completly to imagekit.io now?
For anyone having issues with Cloudinary, we just confirmed with Glide support that they have migrated from Cloudinary to ImageKit.io across all plans.
Since our coded template field in our app referenced Cloudinary and a face focus parameter to autocrop our uploaded head-shot images, this was causing our images to NOT display in our Card component within our app.
Now that Glide uses Imagekit for image storage and processing, we needed to update our template to use the direct Imagekit URL with the fo-face parameter to automatically locate faces and center the crop around them. Below is the new template code to use for that function.
I’m routed here from this thread, an additional unresolved issue to this, as I mentioned there was, upon attempting to right-click-save any image available on the layout, you’re prompted to save to an error file format.
Secondly, also mentioned in the other thread, is that some QuickCharts which had worked fine on Glide for months and years retrospectively, are not rendering now. As I understand (from the number of QuickChart-related posts in the forum), QuickChart is widely and commonly used. Are we getting a compatibility fix in related to ImageKit for QuickChart (and other previously-working image sources)?
Bottom line, Glide should be responsible to 1. ensure compatibility on existing media, 2. disclose this change in service provider and its potential implications with sufficient audibility, because obviously there will be a widespread impact. Millions of images from myriad sources could be silently failing now.