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

"No expiry configured." when AUTO is configured #28509

Closed
cdamken opened this issue Jul 27, 2017 · 7 comments
Closed

"No expiry configured." when AUTO is configured #28509

cdamken opened this issue Jul 27, 2017 · 7 comments
Assignees
Labels
Milestone

Comments

@cdamken
Copy link
Contributor

cdamken commented Jul 27, 2017

Ref: https://github.com/owncloud/enterprise/issues/2148

The message from occ versions:expire and occ trashbin:expire is confusing the auto is configured:

root@snoopy3:/var/www/owncloud/config# occ versions:expire
No expiry configured.
root@snoopy3:/var/www/owncloud/config# occ trashbin:expire
No expiry configured.

Looking the documentation:
old versions should be erase if more than 50% of the quota is used
https://doc.owncloud.org/server/9.1/admin_manual/configuration_files/file_versioning.html
and Trashbin files are older than 30 days
https://doc.owncloud.org/server/9.1/admin_manual/configuration_files/trashbin_options.html?highlight=trashbin

Those procedures are handle when files are uploaded when auto is configured and is not necessary to run the occ command in that configuration.

IMO instead No expiry configured. (where the admin thinks that he forgot to configure something) the message should be: Auto expiration is configured - expiration will be handle automatically.

@tomneedham @VicDeo @DeepDiver1975 Your opinion please.

@cdamken
Copy link
Contributor Author

cdamken commented Oct 10, 2017

@tomneedham @VicDeo @DeepDiver1975 @pmaier1 @hodyroff Your opinion, please.

@hodyroff
Copy link
Contributor

Makes sense, just make a PR ... when its auto we should not say that no expiry is configured. And the auto values must be in the documentation.

@cdamken cdamken added p2-high Escalation, on top of current planning, release blocker sev3-medium Type:Bug blue-ticket and removed bug-analysis labels Nov 15, 2017
@VicDeo
Copy link
Member

VicDeo commented Nov 21, 2017

@cdamken triage is not a proper milestone to work on, but anyway #29646

@PVince81 PVince81 modified the milestones: triage, development Nov 24, 2017
@PVince81
Copy link
Contributor

Likely not critical enough for 9.1, so 10.0.5 only. Let me know if you think otherwise.

@VicDeo
Copy link
Member

VicDeo commented Dec 5, 2017

to be released with 10.0.5

@VicDeo
Copy link
Member

VicDeo commented Dec 14, 2017

Closing as fixed

@VicDeo VicDeo closed this as completed Dec 14, 2017
@lock
Copy link

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

No branches or pull requests

5 participants