-
Notifications
You must be signed in to change notification settings - Fork 666
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
Adapt "public link" permissions to oC server 10.0.4 UI #6192
Comments
I don't think it is too difficult. But this would still be something we would only do in 2.5, right? (because otherwise it would delay the 2.4 release) (I'm wondering if it would not be better to open the browser to share instead of having a native dialog, that way we always have the same ui. (but that would need a decent single sign on mechanism)) |
@ogoffart 👍 for 2.5, no need to rush this over 2.4
I wonder the same; see comments in #5796 and #5797. However, I like the minimalist approach of client's native sharing dialog and all @ckamm's nice redesigns for 2.4/2.5 (meaning I'd still keep it for straightforward tasks)
yup: #633 was one of my main ideas for the upcoming ownCloud hackweek |
yes
==> next week 😉 |
It's a minor change. Fwiw, I'd be perfectly fine with replacing the native UI if we can make it work reliably and smoothly for the user. |
Sorry to open this again but we refined the wording for the web interface and I would like to adapt this for the next client release as well:
|
@michaelstingl looks good, so only wording change 👍 Please don't call the headline "Link properties". Can we agree on just having Permissions? |
It's a straightforward change, sure :) |
(Or just remove the headline as there is none in the WebUI as well)
👍 |
Pretty accurate in 250beta1 with compared to the update from @pmaier1 above: checked on win10 and ubuntu18 with nautilus |
UI for "public link" permissions has been improved with oC server 10.0.4:
owncloud/core#29376
@ckamm What is the effort to bring this to the desktop client? /cc @guruz @ogoffart @SamuAlfageme
The text was updated successfully, but these errors were encountered: