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

[Files external ] Personal mountpoints. Unchecking the option after configuring a mountpoint does not make disappear the configuration in the personal page. #21905

Closed
davitol opened this issue Jan 26, 2016 · 6 comments · Fixed by #21909

Comments

@davitol
Copy link
Contributor

davitol commented Jan 26, 2016

Steps to reproduce

  1. As admin user configure a S3 personal mountpoint
  2. In admin view, in Allow users to mount external storage, uncheck Amazon S3
  3. Go to the personal page.

Expected behaviour

The S3 personal mountpoint configuration should not be shown in the personal page

Actual behaviour

The configuration of the S3 personal mountpoint is visible in the personal page

Note: The mountpoints are not available in the files view (right behaviour)

Server configuration

Operating system: ubuntu 14.04

Web server: apache 2.4.7

Database: mysql

PHP version: 5.5.9

**ownCloud version: ownCloud Enterprise Edition 9.0 pre alpha (daily) Build:2016-01-26T04:16:42+00:00 4c9e328

Updated from an older ownCloud or fresh install: Fresh install

Are you using external storage, if yes which one: yes; S3.
Are you using encryption: no
Are you using an external user-backend, if yes which one: no

Client configuration

Browser: Firefox for Mac OSX

screen shot 2016-01-26 at 09 56 30

screen shot 2016-01-26 at 09 54 42

@davitol davitol added this to the 9.0-current milestone Jan 26, 2016
@PVince81
Copy link
Contributor

@icewind1991 @Xenopathic possible regression

@davitol can you confirm whether this is a regression from 8.2.2 ?

@RobinMcCorkell
Copy link
Member

A quick test shows that while it continues to be displayed in the UI, it correctly does not get mounted, and doesn't display in the files view. This raises an interesting question: do we want to forcefully remove any mount types that have been disabled by the admin (like 8.2 behaviour) or do we want to notify the user that the backend is no longer available by a greyed row or something? Then again, in reality this is something that will happen very rarely, so perhaps just going back to 'forcefully remove' is best, and it's not worth improving.

@PVince81
Copy link
Contributor

If this behaves like in the past then we can keep it on sev4-low and think of @Xenopathic's suggestions later.

@RobinMcCorkell
Copy link
Member

Personally I don't think it will ever be worth improving this beyond the 8.2 behaviour, the only situation where it actually becomes visible is when a user sets up a storage with a given backend, then the admin decides they shouldn't be able to mount it. In such cases one would hope that the admin sends out a notification email to their users telling them of the configuration change that is about to occur

@davitol
Copy link
Contributor Author

davitol commented Jan 26, 2016

If this behaves like in the past then we can keep it on sev4-low

In EE 8.2.2 the behaviour is different. When we uncheck the S3 option, the personal mountpoint disappears from the personal page.

ownCloud Enterprise Edition 8.2.2 (stable)

@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

Successfully merging a pull request may close this issue.

4 participants