Url for folders changed after upgrade to NC 28.0.x

ℹ️ Support
,
1

Nextcloud version (eg, 20.0.5): 28.0.3
Operating system and version (eg, Ubuntu 20.04): Ubuntu 22.04
Apache or nginx version (eg, Apache 2.4.25): Apache
PHP version (eg, 7.4): 8.2

The issue you are facing:

I cannot following links for folders in NC 28. If user copy url of nextcloud folder i.e. link with particular fileid and use it in some email or chat conversation by just coping it from web browser url, it is invalid link in NC 28.

Is this the first time you’ve seen this error? : Y

Steps to replicate it:

  1. Upgrade from NC 27 to 28
  2. Try to visit folder direct url for folder https://nextcloud28.our-servers.de/index.php/apps/files/422

In NC 27: browser with folder will be shown.
In NC 28: browser will jump to a root folder. Url is changed / rewritten to https://nextcloud28.our-servers.de/index.php/apps/files/files/422.

I also tried to modified it manually to https://nextcloud28.our-servers.de/index.php/apps/files/files/422?dir=/ which fixed the problem respectively made the url valid and pointing to the right place. Url works, the dir path is inserted and I am redirected in browser to correct folder.

Summary for me:

  • Links has to be changed that “files/files” are included instead of just “files/” and “?dir=/” has to be added

Is it a bug that developers changed urls in a such way or is it an intention? All links to fileids used in my conversation or email messages are going to be invalid links since NC 28 :frowning:

Of course I would like to see NC 27 links to continue to be valid for NC 28.

2

If you go on the three dots of a file or folder and open the details. There is an option to get an internal link that works for everybody with access to that file. It is in the format: https://nextcloud.example.com/f/1132912

Such an option of permanent links is provided to give a simple way to share this and to keep the same format over time.

If I take the GUI-Links in my NC28, they look like (no duplicate files):
https://nextcloud.example.com/apps/files/?dir=/myfolder&fileid=1234
(and for me, the 1234 id for this file is different from the id which I would get for the direct link).
But I use nginx, perhaps there are some changes/updates to apache, especially two times files in the path look a bit strange.

3

Sharing to anybody with the link i.e. permanent link is not an option for our use case. Files should be shared only to users inside a specific group. It will be ok, if the permanent link would be possible to generate without also sharing it “publicly”.

Anyway, we solve it by creating external application which works as proxy / router and translate/rewrite links for users.