Fri, 10 Apr 2026 20:05:43 +0000 https://bugs.horde.org/ticket/5349 can only upload file to non-empty directory if you have delete permissions horde 3.1.4 gollem-h3-1.0.3 (no option for it in the dropdown for ticket creation) using a user who has Show, Read, and Edit permissions: If i create a directory and then upload a single file, I can no longer see the file upload object once the page is refreshed, in that directory. Same applies to directories with files that already exist. If i give the user delete permissions, he/she can then see the file upload object in any directory. I have a requirement to allow people to upload anywhere they have access to but never delete old files (versions). Basically once they post it they have to upload another as opposed to delete and upload in it's place. so they can' t lie about it later by changing the data. :) Did I miss something in the config? Or is this actually a bug. It looked like the upload object was based on edit permissions and not delete from what I scanned through in the code. Thu, 10 May 2007 21:03:35 +0000 https://bugs.horde.org/ticket/5349#t32938 > horde 3.1.4 > gollem-h3-1.0.3 (no option for it in the dropdown for ticket creation) > > using a user who has Show, Read, and Edit permissions: > If i create a directory and then upload a single file, I can no > longer see the file upload object once the page is refreshed, in that > directory. Same applies to directories with files that already exist. What backend are you using? Mon, 04 Jun 2007 23:39:28 +0000 https://bugs.horde.org/ticket/5349#t33850 >> horde 3.1.4 >> gollem-h3-1.0.3 (no option for it in the dropdown for ticket creation) >> >> using a user who has Show, Read, and Edit permissions: >> If i create a directory and then upload a single file, I can no >> longer see the file upload object once the page is refreshed, in that >> directory. Same applies to directories with files that already exist. > > What backend are you using? the file backend. here is a sample of the config: $backends['file'] = array( 'name' => 'BS-ATT Files', 'driver' => 'file', 'preferred' => '', 'hordeauth' => true, 'params' => array( // The base location under which the user home directories live. 'vfsroot' => '/opt/hordefs/BS-ATT', // The default permissions to set for newly created folders and files. // 'permissions' => $conf['umask'] ), 'loginparams' => array(), 'root' => '/', // 'home' => Auth::getAuth(), // 'createhome' => false, // 'filter' => '^regex$', // 'quota' => false, 'clipboard' => true, 'attributes' => array('type', 'name', 'download', 'modified', 'size', 'permission', 'owner', 'group') ); Sorry it took so long to respond, I never saw the previous message until the status changed. Thu, 05 Jul 2007 13:44:44 +0000 https://bugs.horde.org/ticket/5349#t34959 I can't reproduce using HEAD. Anybody else (since I don't know anything about the permissions code anyway, I may not be the best person to have this ticket in the first place). Tue, 17 Jul 2007 07:52:43 +0000 https://bugs.horde.org/ticket/5349#t35218 Unless I'm badly misunderstanding something, this was just a weird typo that disabled editing if a permissions check for deletion failed: http://lists.horde.org/archives/cvs/Week-of-Mon-20070716/069418.html Btw, should users be able to cut items (as opposed to copy) if they can't delete them? Wed, 18 Jul 2007 18:45:08 +0000 https://bugs.horde.org/ticket/5349#t35261 Ok, I know I'm a bit outdated with version 1.0.2 but it is the latest stable in Gentoo. Anyway, clicking the 'permissions' button in Gollem with the FTP backend totally disables all other users' access to the filesystem. There is no warning and no way to back out the change. You have to edit the database and remove the three new table entries for permissions. There should be a warning screen before execution at the least and a way to actually delete the tables from inside horde. Mon, 16 Jun 2008 04:33:26 +0000 https://bugs.horde.org/ticket/5349#t46525