Mindsharp’s FREE Deleted Items Document Library Custom List Template

Posted recently:


This looks like a cool tool.... great that there is no server side install, easy to use and is an amazing showcase of what can be done in WSS with out of the box components like Lists and Content Editor Web Parts etc...

However, I have a couple of concerns with its use in practice.... i dont think it will catch documents that are deleted via the WebDav interface. i.e. open Explorer and use the UNC path to the doucment lib and delete a doucment. I would be happy to be told otherwise if it does indeed do this 🙂



Comments (2)
  1. Andy May says:

    Chris, you’re absolutuely right. If you look at Todd’s notes on his posting, you’ll see that it excludes Explorer view and Datasheet view deletes, but that it does generate a (one time only) pop-up warning the user of this.

    We’re putting both solutions up on our dev boxes here to have a play, but it looks to us as though the ISAPI filter approach better meets our needs.

    OMMV however.

  2. Todd Bleeker says:


    There is a catch all for WebDav deletes that can be implemented alongside my solution: http://www.gotdotnet.com/workspaces/workspace.aspx?id=8437a203-f377-401c-b23d-ae59e6f05b80

    I suggest that you use both. Since most deletions will be from the Web client, they will be self restorable and won’t require or even invoke the ISAPI filter. In fact, a Document Library Event Sink can be used to programatically do whatever you’d like with the "deleted" file or folder. The safety net of the ISAPI filter will be used if permanent deletes or WebDav deletes are used.

    The custom list template is like the end user’s recycle bin; easy for the user to serve themselves and use the self-restore (it will be used most often). The ISAPI filter is like the administrator’s recycle bin and like many administrative tools requires server-side installation and intervention.

    Also, be aware of these facts: Catching WebDav deletions from a custom list template simply isn’t possible. The ISAPI approach didn’t exist when I created this solution and requires a server-side install. Some people cannot install software on their SharePoint servers. I believe that the two solutions work together well to create a complete solution.


    <Todd />

Comments are closed.

Skip to main content