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

Federated shares should use share_folder config setting #540

Closed
ghost opened this issue Jul 24, 2016 · 6 comments
Closed

Federated shares should use share_folder config setting #540

ghost opened this issue Jul 24, 2016 · 6 comments

Comments

@ghost
Copy link

ghost commented Jul 24, 2016

Expected behavior

Remote shares should use the "default folder for shared files and folders other than root".
The received file should be stored in the defined folder.

https://github.com/nextcloud/server/blob/stable9/config/config.sample.php#L1066-L1069

Actual behavior

The received files stored in the root.

Steps to reproduce the behavior

  1. Create a federated file share on server one.
  2. Accept the remote file share on server two.
  3. On server two, take a look into the share folder, defined in config.php.

Server configuration

Nextcloud version:
9.0.53 (stable)

Updated from an older Nextcloud/ownCloud or fresh install:
ownCloud 9.0.3 -> Nextcloud 9.0.50 -> … -> 9.0.53

List of activated apps:

App list

  …
  - federatedfilesharing: 0.1.0
  - federation: 0.0.4
  - files: 1.4.4
  …
  - files_sharing: 0.9.1
  …

The content of config/config.php:

Config report

  …
  'share_folder' => '/Shared',
  …

Is it a bug, a feature, or by design?

@nickvergessen
Copy link
Member

I'd say by design and IIRC the setting is deprecated.

@schiessle @rullzer

@MorrisJobke
Copy link
Member

I'd say by design and IIRC the setting is deprecated.

Really? Since when?

@schiessle
Copy link
Member

No, it is not deprecated... I think it would make sense to use it for federated shares as well.

@ghost
Copy link
Author

ghost commented Mar 10, 2017

Do we have a chance to see this issue fixed in v12?

@MorrisJobke MorrisJobke removed this from the Nextcloud 12.0 milestone Mar 10, 2017
@MorrisJobke
Copy link
Member

I don't think so, because we have still a lot of other stuff to do for v12

@ghost
Copy link
Author

ghost commented Jun 12, 2017

Any news about this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants