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
windows client 3.5.0: expiry date can't be set for shared link #4327
Comments
It appears that the windows client uses the 'default expiration date' and treats it as if the 'Enforce expiration date' option is set.
Note Users will not be able to set the expiration date further in the future than the enforced expiration date, although they will be able to set a more recent date. Also note that users will be able to update the expiration date again at a later point. The expiration date is based on the current date and not on the share creation date. The user will be able to extend the expiration date again whenever a previous expiration date is close to be reached. |
setting the expirations date does not work for many users on different OSes for over 4 month now... |
I have the same issue and it is extremely annoying :'( Literally can't do anything with the date. |
Tried all the server settings available. The behaviour of the desktop client doesn't change at all. The suggested expiry date is always the actual date. I can't change the input in the text field as shown in the screen shot. I can't change the input even when I try to reconfigure the link. To make it short and simple. It does not work. It is a bug! |
Hi, since this issue is a duplicate of #4068 I will close it, but thanks for reporting |
I can confirm 3.5.1 Client solved this issue for windows. Thanks al lot. |
Impossible to change date in text field.
Bug already existed in 3.4.2 Version
Bug exists in 3.4.3 Version !
Bug still exists in 3.5.0 Version !!
Does anybody care?
Server settings like "expiry in ... days" or "force expiry date" have no effect!
The text was updated successfully, but these errors were encountered: