Read carefully this document about webdav and supported clients. Especially part about Internet Explorer http://pubsvn.ez.no/nextgen/stable/4.1/doc/features/4.1/webdav_readme.txt
You might also look on the article: http://ez.no/developer/articles/ez_publish_knowledge_series_webdav_support_in_ez_publish_4_1_now_using_ez_components
We got Webdav working on 4.1, but the folders show up as images or some generic type. Folder class is standard, settings are standard, same thing happening for various webdav clients. Any ideas?
Thx, Sebastiaan
Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.
We had a similar problem a couple of years ago. It ended up being caused by insufficient permissions for a folder which eZ Publish needs to write to for webdav - a temp folder I think. I'm afraid I can't remember (and the email traffic was to a corporate account which I don't have any more) exactly which, but it was under /var.
>> We got Webdav working on 4.1, but the folders show up as images or some generic type.
BTW, we got this issue on a installation that had been upgraded from 3.7 to 4.1.
Fix:
In \kernel\private\classes\webdav\ezwebdavcontentbackend.php: 1. Fix the display of folders: in the function isObjectFolder( $object, &$class ) we had to change $class->ClassIdentifier into $class->Identifier
2. Fix access to the Media folder: in the function fetchNodeInfo( $target, &$node ) we changes if ( $virtualFolder === self::virtualContentFolderName() ) into if ( $virtualFolder === self::virtualContentFolderName() or $virtualFolder === self::virtualMediaFolderName() )
Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.