-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
internal link should open file not directory #22541
Comments
The browser scrolls to the file and highlights it, though in my experience this isn't always very reliable. Thing is - one can't 'open the file' as many file types are simply not supported with an online viewer. I agree with you that it would be nice, though. Perhaps we could at least do that on files that ARE supported in a viewer... |
Thanks for looking into this |
Or the standard Download Menu from the Browser |
If I share a document with 'Share link', than the link leads direct to the document. So when I copy the link to a browser or click the link from an excel cell, the link opens the document! If I share the same document with 'Internal Link', which I would prefer, then the link leads only to the directory of the file. It is not possible, to open the docment, by clicking the link! Why it is possible, in the first case, but not realizable in the second case (which is much more secure)? |
IMO this is a duplicate of #12470 |
I agree, this is a very strange behavior - nevertheless understandable and good, external users must not see the files in the directory. |
This is not a question of authorization, of course only authorized users are allowed to view the files. It is very inconvenient if you click on a link where you expect a file and only a directory is opened. If you use this link as a reference (for example in a mail or in a document), you don't know which of the many files in this folder is meant. |
Does anybody know which users can do triage? I.e. remove "needs triage" and add "to develop" |
#12470 is not really about the internal link but the one that is presented to the user in the browsers url bar, so I'd keep those separate. I think it is kind of debatable which behavior would be expected here, though for files it probably makes more sense to open them right away instead of just scrolling to them in the file list. What do you think @nextcloud/designers ? |
@juliushaertl can you rename that issue #12470 so the difference to this one here is clear? |
The current behavior should be kept, it heavily supports efficency in our company. We often use internal links to files and it is usual, that not only the linked file is of interest but also other files which are kept in the same (project) directory. As long as the linked file is highlighted, there is enough context IMHO. |
Maybe it could do both? So open the directory in the files app and also open the file directly itself? |
Another possible solution could be, that the internal link leads to a selection, where you can decide, if you want to
One of my secret wishes: Open file locally (from my local synced folder). |
If you send an link, refering to a document to person, and only a directory opens and not the document itself, then the user gets confused! Especially in case of a directory with lots of files. Furthermore, if you have a document eg. Excel Calculation, with links to documents like offers or bills, then it is useless to click on one of the links and only a directory with dozens of files gets opened. |
Nice approach! |
cc @nextcloud/designers |
Same problem here: I created a simple notepad for my holidays and just want to quickly open it in edition mode. Currently, I only manage to do that by sharing it (which I don't want): if it is not shared, the "openfile" URL gives me a "download.zip" file. Given the comments, I suggest that we keep the current behaviour for the current internal files links, but add a link attribute (e.g. |
@szaimen you added "needs info" label -- which information do you need? |
@sebastienaubry I agree, albeit with a minor tweak. Regarding how to handle files that don't have a viewer, in asimilar situation Google Drive asks the viewer what they would like to do, with options typically including download and letting the user choose an app that can handle the file type. |
backported to 22 (not 20 nor 21 and it won't be) |
Do I understand the last comments here right, that this was successfully implemented? Do i have to activate it somewhere? Because on Nextcloud Hub II (23.0.3) we still experience the initial behavior of opening the folder instead of the file and i don't find the right settings to change that. |
I also encountered the same problem. |
Works as expected for me in Nextcloud 23.0.5 with Collabora CODE |
I can confirm the behavior @az-bp describes, currently it's not working with OnlyOffice (NC 26.0.1). Is there any workaround/solution for that? |
same problem here. nextcloud 28.0.8 internal link https://xxx.xxx/index.php/f/60449 opens https://xxx.xxx/index.php/apps/files/files/60449?dir=/ with focus on file |
Steps to reproduce
Expected behaviour
should open the shared file
Actual behaviour
opens the directory with the file - confusing as the users with the link does not know the file name
BTW it should work like "external link" which opens the file.
Server configuration detail
Operating system: Linux 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64
Webserver: Apache/2.4.25 (Debian) (apache2handler)
Database: mysql 10.4.8
PHP version:
7.3.21-1+0
20200807.66+debian91.gbp18a1c2Modules loaded: Core, date, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, sodium, session, standard, apache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, imagick, intl, json, ldap, exif, mysqli, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, apc, posix, readline, shmop, SimpleXML, smbclient, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xmlreader, xmlwriter, xsl, zip, Phar, libsmbclient, Zend OPcache
Nextcloud version: 19.0.1 - 19.0.1.1
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from: unknown
Signing status
Array
(
)
List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption:
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36
Operating system: ubuntu 20.04
Logs
Web server error log
Nextcloud log
Browser log
Insert your browser log here, this could for example include:
The text was updated successfully, but these errors were encountered: