(Bug report) Cannot export root note ("Cannot export branch root since it does not exist")

[sigaloid]

Preflight Checklist

• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Trilium Version

0.48.6

What operating system are you using?

Other Linux

What is your setup?

Local + server sync

Operating System Version

xubuntu

Expected Behavior

I should be able to export the root note.

Actual Behavior

When choosing export zip on any other note, the filename in the export dialog is a .zip, but on the root note, it's an HTML file. And even if I export the root note as a HTML file, it doesn't actually create the file.

Export file dialog on root note:

Export file dialog on any other note:

It never saves the file if I export the root note

As well, the web version says this: "Cannot export branch root since it does not exist."

Additional Information

No response

[zadam]

Fixed, thanks for reporting!

[decentropy]

Fixed, thanks for reporting!

@zadam I don't think this is fixed?

I am on 0.58.2-beta ... and when I try to export root, it gives error page "Cannot export branch root since it does not exist."

[sigaloid]

That issue might also be caused by a corrupted database, have you tried running the various database fixes in settings -> advanced?

[decentropy]

I just ran 'check' and 'find & fix'... it said no issues found, and still gives same error.
I then also tried 'vacuum', then 'fix'... still same error.

[zadam]

@decentropy it's a bug in the 0.58 betas, fixed now. Thanks for reporting!

[decentropy]

Thanks @zadam .. Trilium is awesome.

A question (perhaps unrelated), but is there way to have the export respect sorting/order of the notes?
I notice that exporting is not alphabetical, but also not in my custom sorted order. I was wondering if there's way to control the left-menu order on export.

[zadam]

@decentropy the backend data model did not keep the notes sorted, I guess I assumed it's not needed on the backend. But for export it is, it should keep the order as it is defined in the application. I fixed this in the 0.59 branch.