We have downloaded and installed the AST Azure Media Sync for use in our umbraco (version 6.1.3 running in Azure). We were able to successfully install the plugin and upload photos through the Media section of umbraco's back office, but when we select the photos in the tree of the media section or try to embed an uploaded photo on a content page, the photo URLs just keep coming up as "no Media". We are using the regular media picker instead of the image cropper to show a preview of the image uploaded
Our filesystemproviders.config:
Our web.config:
When we upload using the button in the media section, our image shows up in the media folder list:
but when we click one of the images, there is no indication that a file is attached
(what it was doing when it was working)
And if we try to embed the image on our content page, the images are not linked
(what we would see if it was working properly)
We are able to confirm that the images are being uploaded to blob storage successfully, but the reference isn't being saved to the umbraco database properly (or at all). Could we have missed some other configuration?
During the upload process does the package write the server location of the files to the SQL database? Cause that seems to be our root issue. We have the images on the server in the media folder and also in azure blob storage, but when we query the cmspropertydata table for the image path, it's null. The image below shows what is happening now (top rows) and what we'd expect to see (bottom rows) when the images are uploaded to the server.
Thanks for taking the time to help with this! It was actually an issue we had on our end. We were trying to save the location using an incompatible datatype. We changed it to label and everything is working fine now. Your package was working as expected :)
Media is not being retrieved from Azure blob storage
We have downloaded and installed the AST Azure Media Sync for use in our umbraco (version 6.1.3 running in Azure). We were able to successfully install the plugin and upload photos through the Media section of umbraco's back office, but when we select the photos in the tree of the media section or try to embed an uploaded photo on a content page, the photo URLs just keep coming up as "no Media". We are using the regular media picker instead of the image cropper to show a preview of the image uploaded
Our filesystemproviders.config:
Our web.config:
When we upload using the
button in the media section, our image shows up in the media folder list:
but when we click one of the images, there is no indication that a file is attached
(what it was doing when it was working)
And if we try to embed the image on our content page, the images are not linked
(what we would see if it was working properly)
We are able to confirm that the images are being uploaded to blob storage successfully, but the reference isn't being saved to the umbraco database properly (or at all). Could we have missed some other configuration?
Basically this package first uploads images to the server (under media folder) as normal all the Umbraco sites, then copies it to the Azure.
All the images are for the back-office is loaded from the server not from Azure so make sure that you have them all on your server.
During the upload process does the package write the server location of the files to the SQL database? Cause that seems to be our root issue. We have the images on the server in the media folder and also in azure blob storage, but when we query the cmspropertydata table for the image path, it's null. The image below shows what is happening now (top rows) and what we'd expect to see (bottom rows) when the images are uploaded to the server.)_ - Microso.png)
can you check the logs the to see if there is any error related to that? (first umbracoLog table then log files under App_Data\Logs)
the only thing this package does is just to copy media files to Azure and has nothing to do with SQL or cms property table.
I don't see why you get null in the DB.
can you try to uninstall the package to see if upload a media file works or not?
Hi Ali!
Thanks for taking the time to help with this! It was actually an issue we had on our end. We were trying to save the location using an incompatible datatype. We changed it to label and everything is working fine now. Your package was working as expected :)
Thanks again!
Noah
is working on a reply...