Featured Image Slider 1.0 problem

Topics: Administration, General, Writing modules
Jul 27, 2011 at 6:09 AM

Got some problem in when using in Azure. Since all the media are stored in blob storage, which is a https url. However, when I created a "feature", browse a picture and insert it, there was a "~/" added before the link. When I pressed "Save", it said "The media in Picture could not be found". I cannot change the link in the Picture field. Is there anyway to fix it?

Coordinator
Jul 27, 2011 at 9:47 PM

Can you please file a bug in the issue tracker describing how to reproduce this? Depending on how you are inserting the picture, you may have to go and fix the url manually.

Aug 29, 2011 at 10:24 PM

Hi

Was there a resolution to this? 

Could you explain how you fixed it? I have the same issue. 

Aug 30, 2011 at 2:20 PM

I'm the author of the Featured Item Slider module. However, my module delegates handling of the images to the Media Picker Field module. I have not had a chance to test the module in an Azure environment, so I'm not really sure what the problem is. I believe that the Media Picker Field module just wraps the built-in media picker feature in Orchard, which I presume works correctly in Azure. Maybe Sebastien can shed some more light on this.

Sep 1, 2011 at 12:05 AM

Yes, I changed the Media Picker Field to make it work. It was always prepending ~/ to the url, so with Azure storage coming back as http:// it wasn't working so well. Now I check for http and if it's there I don't prepend the ~/.

I'm no expert on Azure storage, but I would have assumed that Orchard would have used it 'internally' so to speak and then served it through the webserver. 

Although serving it directly from the cloud is probably more efficient.

Sep 1, 2011 at 12:05 AM

Yes, I changed the Media Picker Field to make it work. It was always prepending ~/ to the url, so with Azure storage coming back as http:// it wasn't working so well. Now I check for http and if it's there I don't prepend the ~/.

I'm no expert on Azure storage, but I would have assumed that Orchard would have used it 'internally' so to speak and then served it through the webserver. 

Although serving it directly from the cloud is probably more efficient.

Coordinator
Sep 1, 2011 at 6:08 AM

So many scenarios to take into account ... let's try it on Azure and fix it. Id you have a patch that still makes it work locally with and without virtual folders, then I'd be happy to take it.