We have updated our site to Windows azure storage and now it seems that Upfront can not write to none local storage. We can upload images through upfront and we can place large unedited images in upfront. But if we place an image and try to edit the size we get the following error when saving.
Image failed to process. If images are moved from standard storage (e.g. via plugin that stores uploads to S3) Upfront does not have access. (not authorized `https://ideakit.blob.core.windows.net/ideakit-media/2016/08/ChurchKit-example-site-520x294-6417.jpg' @ error/constitute.c/WriteImage/1080)
Is there anyway around this. Even if it requires us to manually overwrite upfront to write to the non local storage. We are fine with updating the file on every update until there is a true fix for this but we are running a customer multisite. So we need azure storage (or some other non local storage if you can recommend one you know works with upfront) or we will end up flying through our local storage. We also must use upfront. We have been testing and working with upfront since October of last year. And we have worked out almost every kink we had and have come way to far to turn back.