Fix for Issue 35 in order to inform the user from a browser client that the file to be uploaded contains illegal characters and give a chance to replace the file name on his/her own or automatically replace the illegal character with '-'.
Fix of Revision: 6b1f43efcd after code review. Rewrite the check condition.
Fix for Issue 35 and for Revision: 8746b05052 concerning the forbideness of '/' in the file name.
Fix of Revision: ec7b8d0b2c after code review. Added a check condition before removing the first and the last slash of the query path.
Remove the first and the trailing slash from the query when searching for a resource
Another fix for setting the auditInfo object by setting AND the user that changed the resource, not only the modification date of the object.
Setting the modification date and setting the auditInfo object to every resource that causes the proper show of permissions to group in every resource.
Rewrite the touchFolder and touchFile methods in order to update only the modification date and nothing else. Add a new method that select the appropriate files tat have permissions to the specific group that is to be deleted.
Recall a faulty previous commit that was related to forbiding the uploading of a file which file name would contain a slash and also adding to some files a copyright year.
Fix for Issue 35, added a note message on creating a new folder or updating an existing folder, informing the user that slashes are not allowed in folder names.The same note is added during the update of file name. Also, the client code has altered in order to forbid the creation or the update of a resource name.At last, don't allow uploading a file which file name contains slash.
View revisions
Also available in: Atom