-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrictions & Guest-App dilemma #81
Comments
The only logical conclusion that I have is if the sharing restriction is enabled, the guest app will be disabled. |
Added Decision for the version that should be ready for 10.0.1 |
Should be possible by throwing an exception on the server side when enabling and put a message in the exception, but not sure if it will be translated.
Will need some JS hackery, JS code from the guests app that wakes up on the admin page in the right section and finds the checkbox to disable it. |
Case 4) also covering Case 3) Restrict sharing to own group: The purpose is to prevent finding existing users (via sharing dialog user search).
|
I think this code makes no sense: https://github.com/owncloud/core/blob/master/lib/private/Share/Share.php#L730 What would be the use case ? Need input from PM |
Updated my comment #81 (comment) according to discussion with @felixboehm @hodyroff @felixheidecke. |
Who can provide an update on what was done here for 10.0.1 ? |
Only owncloud/core#27849 was done AFAIK (I just ticked the box) As for owncloud/core#27847, some use cases seemed to work with @tomneedham's old PR, but not all use cases. |
Last I checked this already worked. The backend refused to send an email but no error was shown, needs proper error handling. |
looks like the duplicate email detection doesn't work correctly in all cases: owncloud/core#27847 (comment). |
@felixheidecke can you take care of the other frontend tasks ? |
@pmaier1 and I just looked at the new implementation idea of guests and sharing with existing users if the email address exists and discovered these dilemmata.
@PVince81 @IljaN @michaelstingl @felixboehm @hodyroff … just to name a few who might be interested ;-)
Decision for the version that should be ready for 10.0.1
The text was updated successfully, but these errors were encountered: