Patches definition history V1.0.x You will find in this section the change history. ARTIO JoomSEF. The procedure to perform a manual backup/restore depends on.
JoomDOC is the only documents handling component capable of WebDAV. Other than that, it offers basic functions and also reveals its poor programming and lack of documentation and support. If documents handling is a core functionality of your website (along online editing) my strong advice would be using joomDOC just for webdav and use other components for the handling part.
We bought two enterprise licenses and struggled to have webdav working. On the top of that, there're lots of incompatibility between joomdoc and other joomla components.
4 of the joomdoc has been recently revised after found not working with joomla v.3.3.0 and v.2.5.20. In conclusion, we managed to have joomdoc ent working but the amount of work required for the task was discouraging us as the product, at its current maturity level, is not reliable at all. In my opinion, overall it is good enough.
Quite easy to install, quite easy to manage from the back end. Really good navigation module. Simple translation file. The amount of clicks which needs to be done, to actually add document to directory could be less. Also, would be great to make it a bit more user friendly for admins. Took me a while to understand how it works.
And possibility to have Captcha check or time countdown before downloading would be a good future development. But as I said, overall, really good. I really wanted to like this extension. It's the only free document management component that fully integrates with the Joomla ACL that I could find. It looks pretty good too, but it's just too quirky and obscure for users.
The concept of adding a document to a file for metadata and permissions is seriously confusing. The work 'document' means different things depending on where you are too. And it's buggy. Creating a document on a file in the front end adds a record to the database, but it doesn't show up after saving. It knows there is one there because if you try to add another one it fails, but you can't see it in the back end either so it has to be deleted from the database.
Every time you perform an operation on a file, it returns to the root folder instead of staying on the page you are working on. It took me ages to work out that you need 'Access Administration Interface' permissions to edit metadata on the front end. Back to the drawing board.