Submitting this to the Ideas portal per Steve Bruner (Arc). As he stated in (ACS-16084):
Resizer versions of images are not removed as a matter of course on photo deletion.
Composer / Photo Center users expect removal/unpublishing to be as unsurprising and immediate as other day-to-day editing interactions, but the backend does not tell users of the above design choice.
This is causing image endpoints to remain publicly reachable after a post has been unpublished. Additionally, this burdens us with trial and error to discover which endpoint URLs have leaked. Our SEO and Support teams then must keep coordinating with Arc reps and often iterate two times after Arc has thought all internal assets removed. If that extra effort isn't expended from Arc and our teams to take care of these endpoints manually, Google search results will continue to see the unwanted content and cache it for an extended period.
There is sometimes pending litigation behind image removals. For special situations like this, an ACS ticket is usually created by Support to submit to Arc flagging the item. Arc has informed us that the deletions from image cache are done manually in those cases.
We have hundreds of users and even assuming full knowledge of this Photo Center design issue and zero confusion lodging ACS tickets, a max of 30 accounts are allowed to submit those in our organization. Those are commonly set aside for developers, internal support staff and some managers. That membership isn't even exposed by Arc for emergency changes. This shows that escalating a day-to-day deletion to Arc does not scale.
Please automate these removals fully.
Thank you
Guest
