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

"Copy public link to clipboard" should autocreate a link share even if expiry is required #7061

Closed
ckamm opened this issue Mar 1, 2019 · 9 comments
Assignees
Labels
Enhancement feature:sharing ReadyToTest QA, please validate the fix/enhancement
Milestone

Comments

@ckamm
Copy link
Contributor

ckamm commented Mar 1, 2019

Follow up from #6356 due to concerns raised by @lexo-mfleuti. See #6356 (comment).

Currently the client doesn't autocreate a link share if expiry is required. It could do it though and use the specified default expiry offset.

@ckamm ckamm added this to the 2.6.0 milestone Mar 1, 2019
@ckamm ckamm self-assigned this Mar 1, 2019
@lexo-mfleuti
Copy link

Context menu idea
Screenshot: draft of how it could look like
owncloud-context-menu-draft

Configurable context menu
It would be great if the user could select which context menu elements are needed to keep the context menu as compact (efficient) as possible.
tortoise option dialog

@michaelstingl
Copy link
Contributor

Currently the client doesn't autocreate a link share if expiry is required. It could do it though and use the specified default expiry offset.

@ckamm works fo me!

2nd step could be, to bring all menu entries to the root level of the context menu. Visually I think this is a mess, but for efficiency it totally makes sense…

ckamm added a commit that referenced this issue Mar 6, 2019
Previously it gave up if "expiry required" was enabled. Now it'll create
a link share per day with the default expiry for these setups.
ckamm added a commit that referenced this issue Mar 6, 2019
Previously it gave up if "expiry required" was enabled. Now it'll create
a link share per day with the default expiry for these setups.
@ckamm ckamm modified the milestones: 2.6.0, 2.5.4 Mar 6, 2019
ckamm added a commit that referenced this issue Mar 7, 2019
Previously it gave up if "expiry required" was enabled. Now it'll create
a link share per day with the default expiry for these setups.
@ckamm ckamm added ReadyToTest QA, please validate the fix/enhancement and removed PR available labels Mar 7, 2019
@guruz
Copy link
Contributor

guruz commented Mar 11, 2019

@lexo-mfleuti Can you test the shares with expiry using https://download.owncloud.com/desktop/testing/ownCloud-2.5.4.11614.11431-rc1.msi and report back if it works?
For your other comments (configurable context menu), I think it's better to create a new issue as this one here is really just for the bugfix of the link creation (thanks!).

@lexo-mfleuti
Copy link

@guruz Just tried it out. The bug is fixed. Very nice thank you! I can now share files much faster already. Though it would be very cool if you could also change the layout of the context menu to something like I explained above. That would be the dream ;)

@michaelstingl
Copy link
Contributor

Is the link creator aware that the created link will silently disappear after a while?

@lexo-mfleuti
Copy link

No, what do you mean by "silently disappear"? You mean like "removed from clipboard"?

@michaelstingl
Copy link
Contributor

In this case, a max. expiration date has been set by the ownCloud server admin. The user then creates a link with the desktop client that's available in the clipboard. But the user isn't aware the link has an expiration date. After expiration, the link disappears and is no longer valid.

@ckamm adding the expiration date/period to the context menu entry?

@lexo-mfleuti
Copy link

@ckamm adding the expiration date/period to the context menu entry?

I think that would be an even better solution solution than what I suggested in my screenshot above. Like
Copy public link to clipboard (link validity: 26.03.2019)

@ckamm
Copy link
Contributor Author

ckamm commented Mar 12, 2019

I'm glad it works! The further ui refinements don't fit into 2.5.4. I'll make new tickets against 2.6. This one seems done to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement feature:sharing ReadyToTest QA, please validate the fix/enhancement
Projects
None yet
Development

No branches or pull requests

4 participants