Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
We have been using UmbracoFileSystemProviders.Azure for media extensively in Umbraco 7 on Umbraco Cloud for years and it worked very well in different scenarios.
When we tried to deliver Umbraco 8 sites on the cloud with Our.Umbraco.FileSystemProviders.Azure.* we can't get it to work reliably unfortunately.
Using the most current version(s) of UmbracoFileSystemProviders.Azure from
GitHub on a Umbraco 8.1.4 instance, the media items themselves get transferred by Deploy (from DEV environment to LIVE environment), but the actual media files are missing.
What I'd like to know is if somebody has this working? Thanks!
Here's two screenshots to illustrate:
I tried to debug it and it seems like the azure provider is not even called/used by Deploy. Logging is set to the extreme and the log shows no sign of activity for the Azure lib like it should according to the source code for the latest build. However, there is "read 'umb://media-file/rufh1kig/somefilename.png'" and such.
On the contrary, I do indeed see activity on the storage container, and it is reporting some errors and the times correlate with the deployments of the test media item (also there is no other activity on the storage):
Does anyone have a smart idea how to debug this better?
I would be grateful for any heads up!
We debugged further and double-checked the settings.
The errors in the Azure logs are there even when uploading directly to each environment (picking media and uploading which is working and did so from the beginning).
So the Azure Blob "ClientOtherError" don't seem to be linked to the issue.
We also debugged (stepping through even on localhost) with alpha4 of the v2 azure ifilesys provider and AddFile doesn't get called on restore from Cloud (only way do run a debugger, so we used the reverse direction to pull from the dev instance down) but browsing/querying does get called.
With the help from Jeavon we dug deep and discovered, that there has been introduced a new property CanAddPhysical on the interface which the v2 provider doesn't implement right now (throws NotImplEx)
The exact scenario works in Umbrao 7 on Umbraco Cloud with the Community Azure Provider v1.
We tested this on a production site (v7) on Cloud with this settings:
From what we discovered it seems, in Umbraco 8 with Azure Storage Deploy doesn't "just" run the whole pipeline "like a local upload" when it's getting a media item transferred but believes in some "shortcut"? As it stands now, I suppose it doesn't actually (even attempt to) transfer any file, but just the media item ("meta"). IMHO this is why in Umbraco 8 the media file is missing.
The question is why does CanAddPhysical exist in v8 when it didn't in v7 and what's it's exact purpose/intent? Also, can a virtual provider (e.g. Blobs) say they "CanAddPhysical"? 🤔
It looks like we would need to implement the new property and simulate the AddFile method with blobs?
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted