Actually, there was a module for this:
https://xoops.org/modules/repository/singlefile.php?cid=101&lid=1731

Unfortunately, I think it needs to be upgraded to work with XOOPS 2.3 and higher.

Does anyone have a specification of what is different in the language files of 2.4.0 Final compared to RC?

Not having a long history of PHP and MySQL programming, I find it rather difficult to work with updating old code (e.g. old modules) to be compatible with the latest versions of PHP and MySQL, since I don't know which functions etc are not supported in different versions (yes, I can look at the error log in XOOPS, but that may just show the symptom and not the root cause of a problem, if you know what I mean).

It seems to me that this shouldn't be an uncommon situation, so my question is, are there any tools/environments which let's you check your code to identify syntax errors, calls to deprecated functions etc?

I have been looking all over, but haven't really found any. Can it really be so, or am I just looking in the wrong places?

Can we add this to the FAQ?

It works!

Regarding allowing names for unregistered comments, is it on the official feature request list? It seems that shouldn't be that big of an issue to add.

Regarding, the URL rewrite, is that on the list? I guess that significantly more complicated though...

First of all, is it even possible to set general permissions on root level? I haven't found a way except for doing it on document level.

Second, I do get the same notices, but once again they seem to cause no errors.

Third, propagate permissions works fine without any errors or notices. Regarding the disappearing of the setting, maybe you forgot to save the setting by klicking on update setting before you clicked on propagate permissions?

1. It works fine creating and deleting Permission Groups. Regarding modifications to permissions, perhaps the rather unintuitive user interface is fooling you? After you have selected the relevant users and/or user groups, you must use the update permissions button at the bottom of the page, not the update button at the top of the page, which only updates the properties of the document.

This behaviour is repeated on several admin pages, with certain settings being connected to certain submit buttons. Now, if I could only figure what the permission groups are actually used for... (and what are those permission to change o e g u ???)

2. Yes, it works fine to upload a document, edit and allow permission for the registered user group and update permissions. When I log back in with my registered user, it is fully accessible. Are you sure that you are looking in the right place in the folder structure? Are you sure the permission was saved?

As I said in a previous post, I have only played around a bit with DMS, but so far it seems to work quite well actually (and it will work even better after I fix the order of that undefined variable , but I've found out it doesn't affect the page breaks). I think the biggest drawback of this module is its unintuitive user interface, but that is not a showstopper to me, but rather something that I will have to compensate for by creating user guidelines for the user.

Also, let's hope someone eventually picks up on this module and develops it further

Hmmm, that may be. I gave up trying to force a page break after 22 docs uploaded

Now, don't get me wrong on this one. I'm not questioning anyone. I just want to fully establish if there are any bugs and if so, how severe they are and if they can be fixed.

@Abu: Can you please provide some more examples of bugs?

Dealt with or not, while I do get that notice in debug mode, I have not yet seen any real effect of it. It works perfectly fine to upload documents as admin and share to the registered users group.

I'm really interested in this because I'm about to start a project that will rely heavily on document management, so if these bugs are for real (they may very well be, but that remains to be proven) and there is no other alternative to DMS, I may very well be forced to throw XOOPS out for that one and I certainly wouldn't like that