Public share - cant browse

[xavi-GH]

Describe the bug
Linking pages being logged in work, when you make them public you cant.
In recent previous versions of Collectives we didn't have that issue.

To Reproduce
Steps to reproduce the behavior:

1. create new collective
2. create page1 and page2 at the same level
3. create page3 within page2(nested)
4. in page1 create a link to page3 via: smart selector or drag&drop (drag page3 to page1)
5. both links, being logged to nc account work
6. now, make a public link in the collective you created (root page)
7. open that public link in a private browser, now if you click both links in page1 fail, they open a new tab and request login to nc account
8. you can browse to page3 browsing manually from the left menu, but internal links fail to go to page3
9. if you copy public url link of page3 and paste it into another link in page1, it opens a new tab when accessing from public, but you cant browse pages within same tab.

Expected behavior
Internal browsing of links are expected to work as in any other wiki alike app

Screenshots
proposed schema for testing:

Server details:

• Collectives app version: 2.16.1
• Nextcloud version: 29.0.11
• PHP Version: 8.2.27
• Database: MariaDB 10.11.6

Client details:

• OS: Debian
• Browser: Firefox
• Browser version: 128.7
• Device: desktop

Logs

Nextcloud log (data/nextcloud.log)

Insert your Nextcloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...

To make collectives shareable among public users, it is important they can browse doc smoothly, many thanks!

[estux]

Hello, this is a known problem...as I (and others) already reported it some months ago!
(At that time) I also tried to find and list some common problems with internal links between pages and sent a quite exhaustive report of UI/UX issues to the devs.
The main dev opened this issue to track them: #1573
but the work seems not started yet.

EDIT: I'm sorry, as time passed I forgot the right issue to link here (as I opened some of them in a short amount of time) :)
The issue above still lists some other problems with internal links but I think the right issue to link here is this one #1490 , that should be opened again!