Sunil's Notes: Some important URL's for working with WebDav

In the past i blogged about different WebDAV URL's and how i am having difficulty in figuring out which are the right URL's to use and since now i have some visibility in these things i thought i should list out the difference URL's that we are supposed to use

The WebDav URL always begins with http://localhost:10039/wps/mycontenthandler/dav/, my guess is portal makes use of friendly URL mappings to map all the Dav URLs, basic idea is you can create your own URL schema and use the

/themelist: This URL is administration URL that should be used for registering new theme, when you upload theme folder with this URL, two things will happen first the files will get uploaded to WebDAV file store and the theme will be registered in portal data base (Normally we use xmlaccess script to register a theme)

/skinlist: This URL is administration URL that should be used for registering a new Skin in portal database as well as uploading skin related files to WebDAV file store

/contentmodel/wps.content.root: Should be used for accessing the page information and updating the portal page metadata, you can find more information at Using webdav to manage portal pages

/fs-type1: This is generic file store for hosting static files in web dav

The fs-type1 static file store is divided into multiple folders

common-resources: Should be used to store the static files such as css, images, JavaScript that will be used by more than one theme

iwidgets: folder should be used for storing iWidget.xml file, How to publish iWidget xml in the WebDav store , has more information

layout-templates: The layout templates directory is used for storing all the page layout templates, there is one directory for every template. Surprisingly there is no admin URL for registering layout templates, may be because layouts are not stored in portal database(I cant see layout-template element in xmlaccess export)