kumarsivarajan / mollify

Automatically exported from code.google.com/p/mollify
0 stars 0 forks source link

List of shares disappears when changing permission to "require password" #590

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. Create a Share Folder Upload (i.e share a folder) public, no restriction
2. Edit it 
3. Change permission from "public, no restriction" to "public, require password"
4. Save

What is the expected output? What do you see instead?

Expected output: the list of shares from this folder to continue creating new 
shares

What I see: If I don't change permissions then the list of shares from this 
resource reappears when you edit one of them (ok, normal) but if I edit a share 
and change its permissions then when I return to the list of shares I get an 
empty list. The shares are not lost. When I try to edit the shares again I can 
see all of them but the one I tried to change is unchanged.

When the change is from "public" to "private" everything works. This issue only 
happens when changing the share from "public, no restriction" to "public, 
require password".

This happens when sharing folders or files.

What version of the product are you using? On what operating system?

2.5.24 on OpenBSD 5.2

Please provide PHP error log and any additional information below.

No PHP log generated.

Original issue reported on code.google.com by joaki...@gmail.com on 13 Jan 2015 at 9:17

GoogleCodeExporter commented 8 years ago
Forgot to mention: this error happens when you change a share from "public, no 
restriction" to "public, require password" AND YOU DON'T WRITE A PASSWORD. 

Expected output will be either: 
- an error message and not going back to the list of shares
- ignore the change and return to the list of shares showing the shares, not an 
empty screen 

It seems to change to red the border of the password textbox, but is 
immediately hidden so you don't get notified.

Original comment by joaki...@gmail.com on 13 Jan 2015 at 9:31

GoogleCodeExporter commented 8 years ago
Fixed, will be in next release

Original comment by samuli.j...@gmail.com on 14 Jan 2015 at 6:58

GoogleCodeExporter commented 8 years ago
In .26

Original comment by samuli.j...@gmail.com on 14 Jan 2015 at 4:19