Apparent bug in media optimizer causes image conflict
We've been testing the new Media Optimizer on some smaller sites and have been very impressed in the results. Because these are such small sites we've been using a single MO account for them but setting up a separate Media Source / Delivery Profile with a unique URL for each site which I was under the impression would keep them separate.
However I just ran into a situation where adding a new site with it's own unique MS/DP but with images that had the same name as those in a different MS/DP returned images from the older MS/DP even though the url was different.
Basically for an image domain1.com/art/slides/slide-1.webp with a MS setup to use the web address domain1.com and a delivery profile setup to serve the image as ourname.mo.cloudinary.net/domain1/art/slides/slide-2.webp
When we setup domain2 with it's own separate Media Source and a Delivery profile ourname.mo.cloudinary.net/domain2 that is configured to use the domain2 Media Source....we still get slide-1.webp from the domain1 configuration.
I was able to invalidate the cache on the 2nd url and they are now both returning the correct image. But with a limit of 20 cache invalidations at a time it isn't very practical to try and go in and manually invalidate all links on each new site. And with dynamic content on the sites it's highly likely that future conflicts may occur as site owners add new images.
Is this behavior intentional and I'm misunderstanding the point of media sources and delivery profiles - or is this actually a bug?
Post is closed for comments.