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

How to unshare folders/files from expired users after upgrading from OC5 to OC7? #15283

Closed
gig13 opened this issue Mar 27, 2015 · 9 comments
Closed

Comments

@gig13
Copy link

gig13 commented Mar 27, 2015

In ownCloud5 there were expiration of shares available for the users. When upgrading to ownCloud7, this feature is missing, and we wanted to know how to expire/remove these "shares" for all of the user shares that are on the existing system.

There are thousands of users, so this is not something that each user can do individually as a part of operations. How can we do this in a quick and efficient manner?

@MTRichards @bboule

@karlitschek
Copy link
Contributor

@PVince81 @schiesbn

@MorrisJobke
Copy link
Contributor

There is an option to expire public link shares. I wonder that back in ownCloud 5 also normal user-to-user shares were expired. I thought the checkbox in the webinterface was just separated more and the expiry date was also send for new shares if the user has set that to a date.

cc @jancborchardt I thought you were also involved into the process of dividing this functionality. But I doubt, that there was a global option. I couldn't find one in the web interface (admin settings)

@butonic
Copy link
Member

butonic commented Apr 8, 2015

@gig13 Do I understand correctly that this is a one time action for the migration? then we could create a simple SQL query to remove all user / group shares with an expiration date, if that is what is wanted. What db is used?

@gig13
Copy link
Author

gig13 commented Apr 8, 2015

@butonic @bboule
We will need to discuss if it is one time for migration or custom add on to enable older functionality.

@MorrisJobke
Copy link
Contributor

Ref #15459

@bboule
Copy link

bboule commented Dec 30, 2015

@gig13 looks like this is done and checked on for 9 do you need a backport or are we good?

@gig13
Copy link
Author

gig13 commented Jan 14, 2016

@bboule
I do not have a reference for this case, no further comments

@MorrisJobke
Copy link
Contributor

I do not have a reference for this case, no further comments

So closing this?

@lock
Copy link

lock bot commented Aug 6, 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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants