Sharing with full path

ℹ️ Support
1

Hi everyone,

ist it possible to share files or folders so that receivers see them with full path (before maybe renaming them) like

folder1/folder2/file1.txt ->
folder1/folder2/file1.txt

And if applicable is there a difference if folder1 is a group folder?

Thanks!

2

maybe you wanna look into this app here?

https://apps.nextcloud.com/apps/sharingpath

i think it could be very helpful in your case :wink:

3

Thank you, but that’s not what I meant.

I want the full path to be available in the root folder if the receiver’s file-app. Not only the shared file file1.txt as usual.

4

Then, you should probably use the groupfolders app.

5

@decaflo
You can share a folder structure like this example: https://nc.nl.tab.digital/s/S3TBywZ2f9JLHew
In this example (folder “Images” there are three folders and a few picutres.

But full path makes no sense because:

a.) why?
b.) perhaps the sender want move it in future in another path
(my example is in a path named with the month “July” and nobody must know it)
b.) perhaps the receiver move it in a own path without source pathes
(i think the receiver do not like my folder “July”)

6

Here is an introduction to how you can use groupfolders to achieve exactly what you want:
https://help.nextcloud.com/uploads/default/original/3X/5/f/5fa9a8feeacb545560a8b8e5d309f38c7c66cb5c.png

Here is the whole article:

7

a) I have a group folder shared within a group. In this group folder there is a subfolder which has to be shared with another user not member of the group. I want this person to see the full path to have the same structure as the group. THis can be achieved by creating a folder with the same name as the group folder and moving the shared subfolder into it. But maybe there is a simpler way to achieve this.
b (twice :slight_smile: this is a general problem with shares. In general renaming a share does not rename it in the receivers filesystem, only the initial name is set. This is fine.

8

Thank you, I will try this!

9

decaflo, have you found solution?

10

This is useful feature, I hope one day it will be default behaviour, or at least a choice.

a.) why?

To have identical structure on all systems. Example from CGI production: when master project file will be opened, it will be able to find and download all necessary supportive files like caches, textures, 3d models, and download them using virtual files feature.

b.) perhaps the sender want move it in future in another path

So it should be moved on every connected machine, and if it’s not shared folder, access will be lost.

b.) perhaps the receiver move it in a own path without source pathes

So it should be moved on every connected machine, and if it’s not shared folder access will be lost. This is managing issue, no need to resolve it on this level. To worn a user at max.

1 Like