Recently I installed Azure Blob Storage Provider and found that Courier disrespects the custom Media FileSystemProvider. Upon transferring, media files are being saved into default Media folder on the target machine, rather then on Azure blob storage. If I upload media on the target machine using Umbraco backoffice interface, it saves media correctly on the Azure blob storage.
Is the suggested solution of writing a custom event handler is still the best, or there is a better option in the all-new Courier?
I wonder should this be considered as a bug? In my view, extending media provider should affect all higher level system components, i.e. should be transparent for Courier.
I am using the latest Courier 3.1.1 on Umbraco 7.6.1
Umbraco Courier and Azure Blob FileSystemProvider for Media
Recently I installed Azure Blob Storage Provider and found that Courier disrespects the custom Media FileSystemProvider. Upon transferring, media files are being saved into default Media folder on the target machine, rather then on Azure blob storage. If I upload media on the target machine using Umbraco backoffice interface, it saves media correctly on the Azure blob storage.
I found this old topic:
https://our.umbraco.org/forum/umbraco-pro/courier/61152-Using-Courier-with-custom-FileSystemProvider
Is the suggested solution of writing a custom event handler is still the best, or there is a better option in the all-new Courier?
I wonder should this be considered as a bug? In my view, extending media provider should affect all higher level system components, i.e. should be transparent for Courier.
I am using the latest Courier 3.1.1 on Umbraco 7.6.1
Did you ever find a solution other then the custom event handler.
Have hit this issue with a few projects now, and wasn't sure if there is a nicer fix for this or not yet.
is working on a reply...