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
Describe the bug
A mangled link href can cause Text to fail to load (partially or completely) a document, making it unrecoverable (at least, not without ssh-based surgery and an idea of what to look for). Rich-text is also disabled but that doesn't matter much because it's unsaveable, too.
VSCode and GitHub can render these mangled hrefs fine, and it would be nice if NextCloud strove to match that, but on top of that Text itself seems to have been responsible in my case for mangling the link. I had a long-running document I'd used for over a year and suddenly I found I couldn't edit it.
Close and reopen it; it will be blank, or maybe contain only partial content.
I'm not sure what the pattern is; in fact in my testing I went from seeing "etc etc" a couple times in a row to a blank page, with no changes made to the actual file on disk in between.
Verify the contents under ssh to see what's actual saved on disk
Re-open it and try to use the rich-text features; none of them work Expected behavior
The document should remain readable and editable. Malformed links shouldn't accidentally make the entire file inaccessible.
Screenshots
Case I
Case II
Create and save a file:
Paste the mangled link in:
On reopening the file is missing most of its content:
When trying to add more content, rich text is no longer active, and ...
...nothing is saved on reopening (even though the save icon claimed it was):
Verifying under ssh shows that the document is in the state as of the third screenshot, but the further edit did not take
www-data@org:~/nextcloud/data/admin/files$ cat Bug2.md
# Bug2
- This is a list
etc etc
Copy-paste this link into the document: [Le Palm](https://data=!3m1!1e3!4m6!3m5!1s0xf2d1e9f43f86d168:0x24ff3efacb16eb08!8m2!3d25.0078305!4d54.9942305!16s%2Fg%2F11kpkcd3q9?entry=ttu)www-data@org:~/nextcloud/data/admin/files$
Server details:
Nextcloud version: 29.0.10.1
PHP Version: 8.2
Database: MariaDB 10.11.6
Client details:
OS: Ubuntu
Browser: Firefox
Browser version: 133.0.3 (64 bits)
Device: Desktop
🌟 🌟 And let me say thank you for all the hard work you put into NextCloud. It's such a breath of fresh air for me and my friends from the usual vendor lock-in 🪁 🌟 🌟
The text was updated successfully, but these errors were encountered:
Describe the bug
A mangled link href can cause Text to fail to load (partially or completely) a document, making it unrecoverable (at least, not without ssh-based surgery and an idea of what to look for). Rich-text is also disabled but that doesn't matter much because it's unsaveable, too.
VSCode and GitHub can render these mangled hrefs fine, and it would be nice if NextCloud strove to match that, but on top of that Text itself seems to have been responsible in my case for mangling the link. I had a long-running document I'd used for over a year and suddenly I found I couldn't edit it.
My mangled URL is
The issue seems to be around lacking a domain part to the URL, but I haven't exhaustively tested.
To Reproduce
Steps to reproduce the behavior:
Case I, where the document is totally unusable:
Or, Case II, where the document remains openable but missing content (often the entire content):
New -> Text Document
Add some headings and content
Close and re-open it, verifying that the content is there
Copy-paste this link into the document: Le Palm
Close and reopen it; it will be blank, or maybe contain only partial content.
I'm not sure what the pattern is; in fact in my testing I went from seeing "etc etc" a couple times in a row to a blank page, with no changes made to the actual file on disk in between.
Verify the contents under ssh to see what's actual saved on disk
Re-open it and try to use the rich-text features; none of them work
Expected behavior
The document should remain readable and editable. Malformed links shouldn't accidentally make the entire file inaccessible.
Screenshots
Case I
Case II
Create and save a file:
Paste the mangled link in:
On reopening the file is missing most of its content:
When trying to add more content, rich text is no longer active, and ...
...nothing is saved on reopening (even though the save icon claimed it was):
Verifying under ssh shows that the document is in the state as of the third screenshot, but the further edit did not take
Server details:
Client details:
🌟 🌟 And let me say thank you for all the hard work you put into NextCloud. It's such a breath of fresh air for me and my friends from the usual vendor lock-in 🪁 🌟 🌟
The text was updated successfully, but these errors were encountered: