You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Nextcloud 31 public shares also use the same UI as the files app, meaning the legacy UI is dropped in favor of the new (Nextcloud 28) Vue UI.
Sadly the text app does not work out-of-the-box, meaning if you open a public share and then open a markdown file (any file that text can open) the app fails to show the file.
The problem seems that Text does not detect the public share correctly and thus calls the wrong entry point to create a session.
Describe the bug
With Nextcloud 31 public shares also use the same UI as the files app, meaning the legacy UI is dropped in favor of the new (Nextcloud 28) Vue UI.
Sadly the text app does not work out-of-the-box, meaning if you open a public share and then open a markdown file (any file that text can open) the app fails to show the file.
The problem seems that Text does not detect the public share correctly and thus calls the wrong entry point to create a session.
Maybe you can use this functions for public share detection / share token retrieval if needed:
https://nextcloud-libraries.github.io/nextcloud-sharing/modules/public.html
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Text can open and view / edit the file as with Nextcloud 30 and before.
Screenshots
Bildschirmaufnahme_20240906_164408.webm
Server details:
The text was updated successfully, but these errors were encountered: