-
Notifications
You must be signed in to change notification settings - Fork 817
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
The public share link has been removed with the 3.15 client version. #7751
Comments
Hi. Same here. It was a great feature. Can we bring it back ? |
I have the same problem. It looks like the "shared options" were affected with version 3.15.x for many features. |
Hi All, this is working as expected. |
Then I propose to implement an option which you can check to have it there again, because many users used it intentionally. |
@camilasan Okay, then please turn it off by default and make a setting for those who want it back. As a screen reader user, I find it extremely cumbersome to go the whole procedure, whose accessibility is also not the best, instead of just selecting a context menu item in the File Explorer. |
I am wondering what actually the problem is if you hit it unintentionally. |
I am also missing it dearly since it is my most often used feature on the Mac and iOS. In Dropbox it has always been there and it never was a problem for users. I'd strongly urge the devs to bring it back and if you think it's necessary make it optional in the Prefs. Also: it takes WAY to many clicks on iOS and the Mac to generate a public link. It should need not more then right-click → Copy Public Link or Long-Press (or similarly easy functions) on iOS. This is the main function why we (3 companies) had NextCloud in the first place: drop a file somewhere, right-click, share. |
Goodness gratuitous. This is madness :D It's the same thing with my clients, when somebody shows up and says they don't get the interface, they are the one who give a complaint because they feel obliged to. But everybody happily using it, does not have a need to give feedback. |
I can't believe this has been removed ... this is most of the reason I use the desktop client. Surely this doesn't hinder anybody's use of the program? Couldn't the copy the button just have been moved instead of deleted? The loss of this button actually removes function from the software. How does one copy the existing public link of a share now? |
Strange move to remove the sharing option from a sharing platform. Please bring it back. |
I don't know how many hours I have trained my colleagues/customers and now this? Seriously? Please bring it back as an option (OPT-IN if necessary)... |
Changing this is not in our roadmap at the moment. |
I would like to respectfully add to the discussion that this featrue (right-click, copy public link) is the single most used feature for all of our users. Removing this established context-menu item without a setting to make it optional is an astonishing decision. |
I feel, we need to start a petition. I'm not joking, core devs seem not to grasp the simple idea that right click -> copy link is THE feature of the desktop clients. Let alone blind screen reader users like me, I imagine explaining this to users struggling with modern technology. I'm really unpleasantly surprised why such a step was carried out and why an opt-in setting cannot be introduced. Those small things often degrade the whole experience to nearly unusable levels. |
May I ask whether this was a discussion on the Discourse forum, on GitHub or was it a weight of individual feedback through other channels? |
Please make it an option and get is back please. |
This is complete madness. For all my users this is at least a daily use-case. Perhaps go for a default-lifetime for the link (like 72h or something). But please bring this feature back. |
Hi,
The public share link has been removed with the 3.15 client version.
Could it be possible to bring back this feature ?
Below, a screen from a right click on a folder/file with the 3.14.3 client version (w10-w11 OS)
Thank's
Seb
The text was updated successfully, but these errors were encountered: