Skip to content
Marketing Factory Digital GmbH
Contact
Logo Marketing Factory Digital GmbH
  • Agency
    • About us
    • History
  • Services
    • Consulting, Analysis and Strategy
    • Programming and Development
      • Interface Development
      • PIM/ERP Links
      • Custom Development
      • Seamless CMS Integration
    • Hosting and Support
      • Cloud Strategies
      • Hosting Partners of Marketing Factory
    • Services with Third Parties
  • Technology
    • TYPO3
      • Current TYPO3 Versions
    • Shopware
    • IT Security
      • DDoS Protection
      • Continuous Upgrading
      • Privacy First
    • Tech Stack
      • Commitment to Open Source
      • Technology Selection
      • PHP Ecosystem
      • Containerisation & Clustering
      • Content Delivery Networks
      • Search Technologies
  • References
    • Projects
    • Clients
      • Client List
    • Screenshot of the homepage of the new Maxion Wheels websiteNEW: Relaunch of the corporate website of Maxion Wheels
  • Community
    • Community Initiatives
  • Blog
  • Contact
  • Deutsch
  • English

You are here:

  1. Blog
  2. Blog series "Proper Picture Credits": Part 4 - Remove images completely from the CMS after a warning letter
Picturecredits
  • Legal issues
20.10.2017

Blog series "Proper Picture Credits": Part 4 - Remove images completely from the CMS after a warning letter


The fourth part of our series on proper picture credits explains how to remove pictures after a warning notice has been issued without leaving behind picture copies in the CMS that could be subject to another warning notice.

Part 1 - Picture rights management within your company
Part 2 - Rules for online picture credits
Part 3 - Maintain and manage picture credits in the CMS
Part 4 - Remove images completely from the CMS after a warning letter

Even with conscientious picture rights management, it can occur that you have to remove pictures from the web server that are at risk of a warning. Maybe a time-limited picture license has expired or a picture may no longer be shown for reasons of competition law. The higher the legal risks of infringement are, the more carefully one should proceed with the removal of picture files.

Often, the first instinct after a paid warning is: delete the picture from the CMS file management as quickly as possible. This reaction is dangerous. Because hasty deletion often leaves behind copies of the image file on your own server or servers of third-party providers that are liable to a warning (see legal situation)*. Therefore, it is advisable to keep calm after receiving a letter of warning and to obtain an overview first.

*Supplement from 01.09.2021

In a recent decision of the German Federal Court of Justice it was just stated that the original image only has to be deleted from the server if the link to this image version is still published on the web server. Nevertheless, we still advise you to remove the cautioned images completely and without leaving any residues.

Reconstruction: How did the warning come about?

As long as the image is still available on the server, it can be reconstructed in log files and history which editor had uploaded and edited the image at which time. This data and information should be documented internally. Especially the time of the upload can be of importance later for the calculation of usage license claims by the image author.

In addition, the allegations from the warning letter should be compared with the information documented in the company image rights archive. Was there a transfer of rights that the warning party is not aware of? Did the image originate from an old clipart collection that was later bought up by a new rights user? Was the image correctly identified in principle, but a special condition (e.g. time restriction of use) was disregarded?

Under certain circumstances, clarifying the exact circumstances of the image use may therefore already invalidate the reason for the warning.

Document all places of use: where else is the image included?

If it turns out that the image is indeed being used unlawfully and must be removed, the first step should be to determine all locations where the image is used on the web server.

Show larger version for: Screenshot image link detection in the TYPO3 backend
TYPO3 shows every image usage in the backend. The image links can be edited immediately from here

Very often the image is not only linked in one place in a single article. In the TYPO3 backend, for example, an image file is automatically shown individually and with an editing link, from how many content elements the image file is currently used.

In addition, it is common for the content management system to create a copy of an embedded image file (for different image sizes and compression levels), which are not all removed immediately when the original image is deleted, but are still mirrored to proxy servers or CDN systems if necessary.

Checklist: Removing images without leaving a residue

  1. Does the media library or file management automatically generate its own pages for image display?
  2. Is the image shown in an image gallery or image slider (e.g. on the homepage)?
  3. Is there an article preview that uses the image?
  4. Are there other language versions/translations of the article?
  5. Is the image record linked to other pages or content elements in the CMS?
  6. Does the CMS generate different image variants for "Responsive Images"?
  7. Is a cache server or CDN used?
  8. Was the image possibly in a versioning system and is it still accessible via older version addresses?
  9. Can the image still be found on Google under its own server address?
  10. Was the image used for official social media posts as a share image?

If additional versions of the image are discovered, the URL and name of all image files must be determined and listed. While it was originally sufficient to read the image address from the source code of the page, it is now better to search the finished rendered web page for the image file names. The best way to do this is to use the web developer tool that is integrated in all modern browsers. This is because some image variants may only be inserted into the page by JavaScript.

Remove images only after address documentation has been completed

Deleting image files should not be started until the unique URL addresses of all image variants are available. With the removal of the image from the media library and the deletion of the image links from the affected pages, the majority of the found locations should quickly disappear automatically from the image list. However, problems occur especially with addresses on cache servers and CDN systems. Here, you may need the help of a system administrator or the CDN service provider to permanently delete all image mirroring.

Image overwriting in CMS is not enough

Some time ago, it still seems to be a good solution to simply overwrite an explosive, flagged image in the CMS with a new, harmless image version. But since many CDN systems no longer update files with identical file names, we now advise against this method of image replacement.

Remove warned images from Google

If the critical image has been captured by Google Image Search, it can still be found there for a long time after deletion on your own CMS. In addition, the image will show up in the Google page cache for indexed pages. 

If you have verified your own website with Google Search Console, you can have the affected page or a single image hidden for 90 days. This period should usually be sufficient, since the originals of the images have been removed in parallel.

If you have not yet used Search Console for your own website, you should do so as soon as possible for such an occasion. There are no data protection problems and necessities (as with the use of Google Analytics).

 

Removing images from social media

The situation is more difficult if the image has been used for official social media posts of the company. Unfortunately, there is not much more you can do here than delete the affected posts from your own channels. However, you have no influence if third parties have already shared the images. The legal situation is particularly critical because the social media services were usually granted an unauthorized right to use the disputed file when the file was uploaded. At this point, it can only be pointed out once again that it is safer to only use images with positively and clearly clarified usage rights as share images.

Disclaimer: I am not a lawyer and this article does not constitute legal advice. Always clarify open questions with the lawyer(s) you trust!

This concludes our small series on the topic of correct image credits in the CMS. What experiences have you had with copyright and image credits? We would be pleased if you report on this in a comment.

Karoline Steinfatt

From penniless exotic studies to gainfully internet stuff.

More posts by this author

Get blog posts as RSS feed

All parts of this blog series

  1. PicturecreditsBlog Series "Proper Picture Credits": Part 1 - Picture rights management within your company
  2. PicturecreditsBlog Series "Proper Picture Credits": Part 2 - Rules for online picture credits
  3. PicturecreditsBlog Series "Proper Picture Credits": Part 3 - Maintain and manage picture credits in CMS
  4. PicturecreditsBlog series "Proper Picture Credits": Part 4 - Remove images completely from the CMS after a warning letter
  5. PicturecreditsBlog Series "Proper Picture Credits": Part 5 - the special cases: Memes Collages, Screenshots and AI Images

Please feel free to share this article.


Comments

No comments yet.

Write a comment.

I have been informed that the processing of my data is on a voluntary basis and that I can refuse my consent without detrimental consequences for me or withdraw my consent at any time to Marketing Factory Digital GmbH by mail (Marienstraße 14, D-40212 Düsseldorf) or e-mail (info@marketing-factory.de).

I understand that the above data will be stored for as long as I wish to be contacted by Marketing Factory. After my revocation my data will be deleted. Further storage may take place in individual cases if this is required by law.

  • Data privacy policy
  • Legal notice

© Marketing Factory Digital GmbH

Picture Credits
  1. "Picture credits in the footer of a web page": Bildcollage aus Public Domain Bildern
  2. "Screenshot image link proof in TYPO3 backend": © Karoline Steinfatt / Marketing Factory Digital GmbH