Saturday, July 31, 2010
 
   
 
How to Setup a WebDav enabled root folder   Minimize
Location: BlogsOpenDNN blogOpen-DocumentLibrary    
Posted by: Xepient Solutions 7/27/2010
A few easy steps to enable WebDav on your server, and take advantage of the power of direct server editing.

Prerequisites: Create an O-DL root folder

Through the O-DL interface, You'll have already created a documents root folder, that resides under the "/Portals/[0]" directory.

The is the virtual directory where you have installed your DNN application.
The [0] is the default parent portal id. If you have installed O-DL in a child portal, the [0] directory will have a different number or name.
We'll call the documents root folder "O-DL root folder" and it will be located "/Portals/0/O-DL root folder"

 

IIS 7.5

 

1) Go to IIS Manager and select the WebSite that you want to configure to use WebDAV. It could be Default Web Site or other. It's important to select the WebSite although you had installed DNN as a virtual directory or an application under some WebSite.

2) Double click on "WebDAV Authoring Rules" icon.

3) Click on "Enable WebDAV" on the right Actions panel. This setting is only visible in the WebSite, not in virtual directories, applications or folders.

4) Click on "Add Authoring Rule".

5) On the "Add Authoring Rule" dialog select All content, All users and mark all the permissions. If you add these settings over the WebSite, they will be inherited by all the virtual directories, applications or folders under it. NOTE: If you added an authoring rule with the same options on a virtual directory, application or folder, you'll need to remove that rule from the places where you created it and then, create the rule over the WebSite.

6) On IIS Manager, select the ODL root folder and click on Authentication. The root folder is usually Portals\0\root.

7) Make sure that Windows Authentication is enabled for the ODL root folder.

8) On Windows Explorer, navigate to the ODL root folder and open its properties dialog.

9) On the security tab of the properties dialog make sure that Everyone, Network service and IIS_IUSRS have full rights on the folder.

 

Note: If after configuring the above, there are still issues with read-only documents, try this: configure the application pool to run in “classic mode” and add a registry key to enable documents to be written: http://support.microsoft.com/kb/870853

 

 

 

IIS 6

Step 1: Enable WebDav service extensions

Open the IIS Manager, and click on the WebService Extensions folder in the navigation tree on the left panel.
In the list of the Web Service Extensions that will appear on the right, you will see WebDav. If it is disabled, click on the Allow button.

 

Step 2: Make the O-DL root folder a WebDav enabled folder

Open the IIS Manager, and navigate to the folder corresponding to teh O-DL root folder in the navigation tree on the left panel.
In this case it will be "DotNetNuke4.7.0/Portals/0/O-DL root Folder"



Right click on the root folder, and wclick on the properties option in the context menu that will appear.
The Properties window will appear. Click on the "Write" checkbox as shown in the image below.

 

Step 3: Enable WebDav in O-DL

Go to the module settings and enable WebDav as shown in the image below.

 

 

Step 4: Edit the document

Once WebDav is enabled, an additional icon will appear below the download icon (teh icon with teh orange arrows in the image below). Use that additional icon to open the document directly from the server and save any changes directly to the server.

 

Permalink |  Trackback

Comments (11)   Add Comment
Re: How to Setup a WebDav enabled root folder    By djamell on 1/22/2008
I followed the instructions and when I click on the Enable WebDAV ckeckbox and click the "Check" icon I get the following error.<br> <br>"webdav [or some of its options] does not seem to be enabled on the server or, the server response is not a valid webdav response "<br><br>I was running DNN 4.5.5 and upgraded to 4.6.2 and still have the problem.<br><br>Please advise.

Re: How to Setup a WebDav enabled root folder    By host on 1/22/2008
Hi,<br>the check action sends a request to the server (the currently selected root folder), and analyzes the response, looking for some webdav specific implemented actions. If it does not find them in the response header, you will get the message you reported.<br><br>However, this does not really mean that webdav is not enabled in your server or some of the subfolders. It is just a possible warning.<br><br>Go ahead and leave the webdav checkbox selected, and try opening the document as a webdav document. If you followed the appropriate setup steps, it should work.<br>

Re: How to Setup a WebDav enabled root folder    By djamell on 1/25/2008
It works, but it prompts me with a "Windows Authentication" type Login box and I must enter a valid Windows (AD) username and password to open the file. Is there some IIS6 configuration change I can make to remove this? I need to be able to let users outside the Windows AD Domain to open files.

Re: How to Setup a WebDav enabled root folder    By host on 1/25/2008
I suppose you could setup impersonation of a user that has the appropriate rights.<br><br>I am not sure it is the safest way to do it in an extranet.<br><br>In order to setup impersonation, you can do so in the web.config. In this post, <br>http://www.opendnn.net/Resources/Blog/tabid/129/EntryID/17/Default.aspx<br><br>we explain how. (just look at the web.config cahnges necessary. The rest of the article is not relevant).<br>

Re: How to Setup a WebDav enabled root folder    By djamell on 1/27/2008
So this behaviour is expected? In reading the information about WebDAV on this website, including this blog post, you don't even mention it. It's presented as setup, open, and save.<br><br>I think you should revise your site to include the fact that you must have a valid local AD login in order to use WebDAV.<br><br>Perhaps this is also my failing for not fully understanding the underlying WebDAV technology.

Re: How to Setup a WebDav enabled root folder    By host on 1/27/2008
You do not need an underlying AD user. You could allow anonymous access to your webdav folder by allowing the ASPNET or NetworkService account full (or read/write/modify) access to the underlying folder. <br><br>

Re: How to Setup a WebDav enabled root folder    By jeidson on 2/15/2008
This may not be the proper place for this post, but I am unable to even create sub-folders or set permissions, let alone configure the webdav options. I get a {"value":null,"error":null} on almost everything I do once I click the update link. Am I missing something obvious? thanks

Re: How to Setup a WebDav enabled root folder    By host on 2/15/2008
jeidson, can you please write at info[@]xepient. co m<br>with the following details: DNN version, O-DL version installed, Operating system, .NET versions installed<br>Please do not post support questions in this blog.

Re: How to Setup a WebDav enabled root folder    By Scott Allender on 6/13/2008
When I attempt to update a file on the server, I seem to get a link to the file, as opposed to the real file. I followed the steps outlined above, but keep encountering the same issue. Have I misconfigured something?

Re: How to Setup a WebDav enabled root folder    By host on 6/13/2008
Hello,<br><br>you are correct, when clicking the WebDav download button in O-DL, you are really getting a link to the document on the server. Your WebEnabled client (such as MSWord) should then open that file (directly from the server),, and allow you to save any changes directly to the server.<br><br>The fact that what you are downloading is a link, should be transparent to the end user.<br>

O-DL: Enabling WebDav in Open-DocumentLibrary    By TrackBack on 1/7/2010
starting with O-DL version 4.1.1, we will be changing the way WebDav integration is handled. ...
# OpenDNN blog


Your name:
Title:
Comment:
Security Code
Enter the code shown above in the box below
Add Comment   Cancel 
     
Search the Blog   Minimize
     
Blog List   Minimize
     
Blog Archive   Minimize