Hi Connie,

What version of Umbraco are you using? Also what version of IIS? as it sounds like the .air mimetype isn't registered. Checkout the instructions on the main project page for setting up a mime type on IIS 6, or check here (http://blogs.iis.net/bills/archive/2008/03/25/how-to-add-mime-types-with-iis7-web-config.aspx) for instructions for setting one up on IIS7

Many thanks

Matt

PS Still not sure why the dasboard only appears on the recycle bin as I can't replicate it.

Hi Matt,

I am having the same issue - I get "Try Again" every time I try to install the application (after it sits on Installing Application for about 30 seconds).

I am using Umbraco 4.5.2.

I checked IIS7, and it didn't have a mime type for .air registered, so I added one.

Should my web.config file have anything in it to show that the mime type is registered?? I think perhaps my web.config file was checked in to source control when I did the package install, so it may not have been writable...

Any help would be greatly appreciated - I'm really itching to try out the app!

Cheers,

Daniel

Hi Daniel,

If you are using IIS7 then yes, you should have the following in your web.config

<staticContent>
      <mimeMap fileExtension=".air" mimeType="application/vnd.adobe.air-application-installer-package+zip" />
    </staticContent>

You could try installing the air app manualy by running the .air file yourself. If this works, then it's most definatley something to do with the mime type setup. You'll find the air file at:

/umbraco/plugins/theoutfield/desktopmediauploader/desktopmediauploader.air

Matt

Hi Matt,

Thanks for the reply.

As soon as I add the code you mentioned to the web.config file (to the system.webServer node), ALL images in the umbraco admin interface, along with styles in the front end become broken.

This is what I see:

I tried running the app directly, and it worked, but I would like to get it working through the web interface, so that others can install it as well.

Cheers,

Daniel

Hi Daniel,

Ok, that's a little weird. The fact that you managed to install it manually though, does suggest to me, it's almost certainly an issue with the mime type, so I'd keep persisting with it.

Just to eliminate any screw ups with pasting it in the right place, maybe you can give this a go via IIS

http://www.iis.net/ConfigReference/system.webServer/staticContent/mimeMap

obviously setting the extension to "air" and the mime type to "application/vnd.adobe.air-application-installer-package+zip"

Many thanks

Matt

I've been having the same issue - "As soon as I add the code you mentioned to the web.config file (to the system.webServer node), ALL images in the umbraco admin interface, along with styles in the front end become broken.".

I think I've figured out why/when this happens.

If you've already registered the air mime type at the IIS7 level (therefore for all sites), if you the add the same air mimetype to the web.config it seems to break the images/css.

Very weird.  So the solution is either register at the root level only OR register for each website...but not both.

Also note: that the mimetype is in the default umbraco 4.7.0 web.config...so this will cause all sorts of issues when installing umbraco if you have the mimetype registered at the iis level.  You'll need to remove it from the web.config BEFORE installing umbraco.

Hope that helps those who have the same issue.

Trevor

Hey Trevor,

Interesting. I didn't even think of that. Weird that it causes all images to fail though, will have to look into it and see if I can find out why.

Thanks for doing some digging

Matt

Hey Trevor,

Quickly looking into it, I think we might have 2 options

1) Inside the <staticContent> node, start with a <clear /> tag to remove all higher level declarations

or

2) Inside the <staticContent> node, start with <remove fileExtension=".air" /> tag to remove specifically any higher level declarations for the .air extension

I'll do some testing of my own, but though you might like to try them aswell in the mean time.

All the best

Matt

Matt, you're a genious!

Option 2 - adding a remove statement first fixes the issue.

I assume you'll update your package to include the remove statement for those who install DMU into umbraco versions 4.6.x and below?

I think we also need to get the core umbraco 4.7.x web.config changed in the next release to include the remove statement too....as others like myself that have IIS configured in this way have a horrible umbraco installation experience without it.  Do you know how to try and get this into the core?

Cheers, Trevor

Hey Trevor,

Glad to hear it worked. I'll get right on updating the standalone and umb 4.7 version (I can update both).

Thanks for the feedback, it's made sorting it out so much easier =)

Cheers

Matt

Hi Trevor,

FYI I have released an updated version of the standalone DMU with the fix applied, and have also submitted the fix to the core version which should be included in the next bug fix release (http://umbraco.codeplex.com/SourceControl/changeset/changes/0f56abf6fb95)

Cheers

Matt

is working on a reply...