Core: Feature Request - support for aliasing/shortcuts/links
It would be nice to be able to create alias/shortcut/link in ownCloud and have them work when viewed from the relevant platforms Mac OS X/Windows/Unix. Currently such objects seem to be invisible in the web interface or in mobile clients.
In Mac OS X Finder in the ownCloud window I can create one that works,
as is also the case using the ownCloud window in Windows Explorer. But these
aliases/shortcuts are not visible in the web interface or in other ownCloud windows.
andrewbutterfield
All 9 comments
@icewind1991
Niduroki
on 1 Aug 2013
to be honest I don't see the necessity of this feature - can you please elaborate how this would be helpful to the users. THX
DeepDiver1975
on 5 Aug 2013
no feedback -> close
DeepDiver1975
on 6 Feb 2014
Can this be re-opened? It would be a very useful feature! Thanks.
mbressman
on 22 Jun 2014
Necessity : the same as symlinks in unix world or shortcuts in windows world, you can view it as a kind of mount point.
Supporting that kind of feature could allow to assemble collections of files or folders and avoid to duplicate them.
I think its a must have
j33f
on 17 Oct 2014
I think it would be useful. I have a templates folder which I would like sync between home and work. some of my template files are work related (ex: company letterhead and powerpoint templates) the rest are common which I have made many years ago, and use at work and home (template.c template.java, etc). It would be nice to have work and home versions of the folder with common files linked rather than copied between them.
At one point you could do this by sharing via URL with yourself, but that loophole appears to have been closed now.
Enoch247
on 5 Jan 2016
This request should be re-opened IMHO.
Necessities:
-> to allow access from different contextes (=folders)
-> to avoid duplicate files
-> to avoid that only some of the copies will be updated if required
Could be boiled down to a .uri file type (MIME type text/uri-list according to RFC 2483, see https://tools.ietf.org/html/rfc2483#section-5). This file type is presented as a file or folder in ownCloud [1], but is just a common link: If such an object is clicked, the client treats this as a simple link by opening the URL given inside the file [2].
Maybe this requires adaptions in ownCloud, in addition to just processing .uri files:
->To create such a file, the user may click on the [+] icon in the breadcrumbs line. At the bottom of the dropdown list, there's a new option "create shortcut link". In a dialog box, the user may choose to either paste a hyperlink or to browse an object in his file structure. In the latter case, the url will point to an absolute object ID, since the same file may have another path for another user.
-> If a user opens such a file (by clicking on the object in the file list) [3], the client must be able to resolve the absolute object ID mentioned above and see whether he has access to that file. If he has access and the target is a file, the client can open that file (as usual), but if the target is a folder, the client must open that folder.
[1] probably, there are 5 presentations (icons) to be implemented: for files and folders and for other hyperlinks. Some files and folders may show a locked-icon, if the client has no access to this file.
[2] A text/uri-list file may contain more than one URI. Maybe owncloud will only process the first URI or will ask back if it's ok to create multiple tabs/windows -- and at least state the number of URIs contained.
[3] While there's a RFC standard for .uri files and owncloud may learn how to process those files in the browser, there's IMHO no standard across all browsers and platforms how to treat those files if the files are accessed over webDAV.
wintifrosch
on 20 Jun 2016
No necessity?
I don't wanna copy the file 999999 times and put it into 999999 folders, damn what a question, of course its important and a necessity!
Fabi12345
on 12 May 2018
I second this feature request!
Marx1st
on 7 Nov 2018
Related issues
jnweiger
路
4Comments
j-holub
路
3Comments
michaelstingl
路
3Comments
photodude
路
3Comments
mattcatt00
路
4Comments
Most helpful comment
This request should be re-opened IMHO.
Necessities:
-> to allow access from different contextes (=folders)
-> to avoid duplicate files
-> to avoid that only some of the copies will be updated if required
Could be boiled down to a .uri file type (MIME type text/uri-list according to RFC 2483, see https://tools.ietf.org/html/rfc2483#section-5). This file type is presented as a file or folder in ownCloud [1], but is just a common link: If such an object is clicked, the client treats this as a simple link by opening the URL given inside the file [2].
Maybe this requires adaptions in ownCloud, in addition to just processing .uri files:
->To create such a file, the user may click on the [+] icon in the breadcrumbs line. At the bottom of the dropdown list, there's a new option "create shortcut link". In a dialog box, the user may choose to either paste a hyperlink or to browse an object in his file structure. In the latter case, the url will point to an absolute object ID, since the same file may have another path for another user.
-> If a user opens such a file (by clicking on the object in the file list) [3], the client must be able to resolve the absolute object ID mentioned above and see whether he has access to that file. If he has access and the target is a file, the client can open that file (as usual), but if the target is a folder, the client must open that folder.
[1] probably, there are 5 presentations (icons) to be implemented: for files and folders and for other hyperlinks. Some files and folders may show a locked-icon, if the client has no access to this file.
[2] A text/uri-list file may contain more than one URI. Maybe owncloud will only process the first URI or will ask back if it's ok to create multiple tabs/windows -- and at least state the number of URIs contained.
[3] While there's a RFC standard for .uri files and owncloud may learn how to process those files in the browser, there's IMHO no standard across all browsers and platforms how to treat those files if the files are accessed over webDAV.