Skip to content
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

Add capability indicating support of multiple link shares #27622

Closed
ckamm opened this issue Apr 11, 2017 · 14 comments · Fixed by #27709
Closed

Add capability indicating support of multiple link shares #27622

ckamm opened this issue Apr 11, 2017 · 14 comments · Fixed by #27709

Comments

@ckamm
Copy link

ckamm commented Apr 11, 2017

I'm working on adding support for multiple link shares to the client (owncloud/client#5655). I want to make the new UI show only for servers that support it without depending on a server version number. A capability would be nice, but don't see one for this feature yet.

Concrete suggestion: Add capability capabilities/files_sharing/public/multiple to 10.0.

@ckamm ckamm added this to the 10.0 milestone Apr 11, 2017
@ckamm
Copy link
Author

ckamm commented Apr 11, 2017

Note that maybe the server always technically supported multiple link shares per path and it was just not exposed to the user - and what's actually new here is the ui and the ability to name these. In that case the capability should be named differently.

@PVince81
Copy link
Contributor

a ping would have been nice, I'm only seeing this now...

@michaelstingl was this discussed in the context of clients support ?

@PVince81
Copy link
Contributor

"files_sharing": {
          "api_enabled": true,
          "public": {
            "enabled": true,
            "password": {
              "enforced": false
            },
            "expire_date": {
              "enabled": false
            },
            "send_mail": false,
            "upload": true,
            "multiple": true
          },

see "multiple". Only present if public link sharing is enabled.

@davivel @ckamm @SamuAlfageme @michaelstingl

PR here, please review it: #27709

@michaelstingl
Copy link

@PVince81 Awesome, Thanks!

@PVince81
Copy link
Contributor

It's in 10.0.0 RC2, please test

@davivel
Copy link

davivel commented Apr 21, 2017

@PVince81, thanks, we'll do.

@davivel
Copy link

davivel commented Apr 21, 2017

For the record: it's in master now, but not in 10.0.0RC2, not in the tag at least (https://github.com/owncloud/core/releases/tag/v10.0.0RC2 ).

@PVince81
Copy link
Contributor

how come ? I merged it before releasing

@davivel
Copy link

davivel commented Apr 21, 2017

Don't know, but history of master shows the commit after.

@davivel
Copy link

davivel commented Apr 21, 2017

And the daily build doesn't include it either; I patched it to test.

BTW, works for us :) , thank you.

@PVince81
Copy link
Contributor

Indeed: https://github.com/owncloud/core/blob/v10.0.0RC2/apps/files_sharing/lib/Capabilities.php#L70

Ok... my mistake... I saw the thumbs up and thought it was merged and didn't verify...

ckamm added a commit to ckamm/owncloud-client that referenced this issue Apr 21, 2017
Starting from oC 10.0.0 having several public link shares with
different attributes for a path will be supported. This adds
functionality to create, edit and delete these public link shares.

The behavior is currently gated by server version, but should be
adapted to use a capability as soon as one is introduced, see
owncloud/core#27622.

The UI reduces to a single-share version when talking to older servers.

Testing scenarios:
* Link sharing is disabled (by capability, not by theme)
* Required passwords
* Required expiry
* Forbidden 'allow upload' for folders
* New and old servers
@ckamm
Copy link
Author

ckamm commented Apr 21, 2017

@PVince81 Great! I'll update the client to make use of it! :)

@SamuAlfageme
Copy link

SamuAlfageme commented Apr 24, 2017

Tested with client's master and oC EE 10.0.0 RC2 (daily) Build:2017-04-24 and works as expected 😎

@lock
Copy link

lock bot commented Aug 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants