• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 1.1
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      This is probably way out there, but would make life so much easier for collaboration. Essentially most collaboration projects start with a shared network drive and then migrate to an intranet. I would like to get back to the roots with a WebDAV interface to Confluence so those who feel comfortable browsing a file system and saving files on a "network share" will be able do the same.

      Essentially, I see all pages corresponding to folders and any attachments in that folder would appear as files. Any children would be folders within their parent folder. This way people can open up documents and edit them and then store them back to confluence without even opening the browser.

      Using Jakarta slide and writing a custom backend to the Confluence database is a possible solution. I think Slide 2.0 has some file versioning built into it (A feature requested already).

      This feature would allow for group folders within projects for storing information

      Also there should be personal folders (~soandso) so when someone logs into their computer, they're map directly to Confluence.

      I'll keep my fingers crossed for this feature in 2.0

            [CONFSERVER-802] WebDAV access to attachments

            Yes, that does help.

            I guess I'm going to have to "role up my sleeves" and create the functionality myself. When is the the next rev coming out?

            Noah Campbell added a comment - Yes, that does help. I guess I'm going to have to "role up my sleeves" and create the functionality myself. When is the the next rev coming out?

            Noah,

            Yes - currently we've implemented the ability to store attachments in a remote WebDAV server.

            Not yet implemented is the ability to access Confluence attachments from a WebDAV client (ie Confleunce acting as a WebDAV server).

            Does that help?

            Cheers,
            Mike

            Mike Cannon-Brookes added a comment - Noah, Yes - currently we've implemented the ability to store attachments in a remote WebDAV server. Not yet implemented is the ability to access Confluence attachments from a WebDAV client (ie Confleunce acting as a WebDAV server). Does that help? Cheers, Mike

            Confluence doesn't "own" anything on the webdav server. A user with sufficient permissions on the webdav server can do whatever wishes. Confluence is just another client of the webdav. Integrating Confluence permissions and external webdav server permission is almost impossible, unless we bundle a webdav server with Confluence and implement our own store which does permission checks based on Confluence user/groups.

            Ara.

            Ara Abrahamian added a comment - Confluence doesn't "own" anything on the webdav server. A user with sufficient permissions on the webdav server can do whatever wishes. Confluence is just another client of the webdav. Integrating Confluence permissions and external webdav server permission is almost impossible, unless we bundle a webdav server with Confluence and implement our own store which does permission checks based on Confluence user/groups. Ara.

            What about permissions? Since the entire structure is owned by the Confluence "process" when someone opens up the WebDAV folder, how do you prevent them to navigating to other folders that they wouldn't have permission to see?

            Noah Campbell added a comment - What about permissions? Since the entire structure is owned by the Confluence "process" when someone opens up the WebDAV folder, how do you prevent them to navigating to other folders that they wouldn't have permission to see?

            The setup? During setup or later via the admin console you choose whether attachments are stored locally on file system or on a webdav server. Webdav server url, username/pass is all you need to set. Anything else needed?

            Ara.

            Ara Abrahamian added a comment - The setup? During setup or later via the admin console you choose whether attachments are stored locally on file system or on a webdav server. Webdav server url, username/pass is all you need to set. Anything else needed? Ara.

            Just curious what to expect. Is there any documentation on confluence regarding the setup?

            Noah Campbell added a comment - Just curious what to expect. Is there any documentation on confluence regarding the setup?

            Oh Happy Day!...My boss will be happy to hear that this is coming sooner than later. Thank you and I can't wait to test it.

            Noah Campbell added a comment - Oh Happy Day!...My boss will be happy to hear that this is coming sooner than later. Thank you and I can't wait to test it.

            Noah, the feature is implemented We'll release it along a few other features and fixes as 1.1 alpha1 soon. Stay tuned.

            Ara.

            Ara Abrahamian added a comment - Noah, the feature is implemented We'll release it along a few other features and fixes as 1.1 alpha1 soon. Stay tuned. Ara.

            This is an extremely interesting feature. I hope you get it in 1.1.

            Lauri Siljam?ki added a comment - This is an extremely interesting feature. I hope you get it in 1.1.

            I'm glad to hear that you're using a proxy. I was talking with Mike regarding proxy vs. standalone and I'm glad to hear you choose the proxy route.

            I also thought about the slide store. For some reason the notion of editing a file that contains the content as if it were a file just seemed the most logical (I guess that's from modifying html pages). The proxy route is a good choice as well. You could turn your Oracle 9i XDB into the underlying storage for attachments (it's really cool when you include XDB's ability to process xml files) but I digress.

            Any chance on getting the code out in a beta/minor release before 1.1?

            -Noah

            Noah Campbell added a comment - I'm glad to hear that you're using a proxy. I was talking with Mike regarding proxy vs. standalone and I'm glad to hear you choose the proxy route. I also thought about the slide store. For some reason the notion of editing a file that contains the content as if it were a file just seemed the most logical (I guess that's from modifying html pages). The proxy route is a good choice as well. You could turn your Oracle 9i XDB into the underlying storage for attachments (it's really cool when you include XDB's ability to process xml files) but I digress. Any chance on getting the code out in a beta/minor release before 1.1? -Noah

              b1cb4f1d3169 Ara Abrahamian
              noahcampbell Noah Campbell
              Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: