After the migration to v17 we had to reimplement the opensource AWS S3 Media File System Provider which is practically a copy of Azure implementation of a storage provider . It works good, the media can be uploaded and is visible in the backoffice, works as expected on FE with crops and everything. …

Quite a large thread here.. and a solution? [image] Appsettings.json and custom login page speech_balloonQuestions what path are you using? These work for me "LoginBackgroundImage": "../media/zdqkdyk1/reddick.jpg", "LoginLogoImage": "../asset…

It works fine if I have the images in the solution and in its wwwroot directory, but doesn’t work if I try to reference the images that reside in S3 media file system. So the linked discussion doesn’t really help.

Ah yes right there infront of us.. the handler should be using MediaFileManager The recommended approach to obtain a file’s content as a stream is to utilize the MediaFileManager . It is advised to avoid reading the file directly from the server using methods like Server.MapPath . This will ensure…

Opened Features or ideas disucssion: [image] Make BackOfficeGraphicsController use MediaFileManager instead of physical... Setting up the custom backoffice background and logo links in appsettings fails to load the images when the they reside in an external media file system provider. It…

Media File System doesn't work for backoffice logo and background

Questions

mistyn8 (Mike Chambers) April 14, 2026, 9:34am 2

Quite a large thread here.. and a solution?