v0.97.0

[eliandoran]

v0.97.0

Caution

Important Security Update

This release addresses a security vulnerability that could make password-based attacks against your Trilium instance more feasible. We strongly recommend upgrading to this version as soon as possible, especially if your Trilium server is accessible over a network.

For more details about this security fix, please see our published security advisory which will be available 14 days after this release.

Important

If you enjoyed this release, consider showing a token of appreciation by:

• Pressing the “Star” button on GitHub (top-right).
• Considering a one-time or recurrent donation to the lead developer via GitHub Sponsors or PayPal.

💡 Key highlights

• “Books” have been renamed to Collections to better match their intentions.
  • A new collection was introduced, table.
    • See the in-app documentation for more information.
    • Custom table theme for Trilium by @adoriandoran
  • Geomap: The geomap was converted from a standalone note type to a collection.
  • The collections are not displayed directly in “Insert child” in the note tree with predefined configuration such as promoted attributes to make them easier to use (e.g. for calendar, geomap).
• A new editing mechanism was introduced: quick edit. This opens notes for editing in a popup instead of a tab, allowing easy access. This is especially useful for collections, to edit notes without switching context.

🐞 Bugfixes

• Missing note meta. Can't export empty note and involved note tree
• Mermaid notes sluggish
• In-app help confusing due to ligatures
• Geo map: tooltip not showing.
• Nix flake support broke with electron 37 upgrade
• Signing on Windows did not work on the previous release.
• When editing a note in Linux, middle-clicking a note title in tree pane triggers a paste action
• Editor not focused after switching tabs.
• PDF file preview: inconvenient 10px scrollable margin at the bottom.
• Calendar view:
  • Subtree children not displayed when in calendar root.
  • Title changes to events not reflected.
• Attributes Dialogue Doesn't Display for existing attributes
• Issues on Prometeus dashboard due to timestamps
• Ckeditor (re)-creation likely causes important lagging when coming from code note

✨ Improvements

• Export to ZIP:
  • Improve error handling
  • Improve handling of notes with empty title.
• Tree context menu: reorder the note types of “Insert (child) note...” by @adoriandoran
• Note map: add attributes to include or exclude relations by @kieranknowles1
• iframe sandbox allow popups
• Badges for the note type context menu by @adoriandoran
• The “Book/Collection Properties" ribbon tab no longer focuses automatically.
• Geomap improvements:
  • Geolocation now displayed in the context menu.
  • Context menu for empty spaces on the map, for quickly viewing the location or adding a new marker.
  • Adding markers by drag & dropping from note tree.
  • Read-only mode to prevent modification such as dragging.
  • Calendar View: Added options to hide weekends & display week numbers directly from the “Collection Properties” in the ribbon.
• Tree Context Menu: relocate the "Duplicate subtree" menu item by @adoriandoran

📖 Documentation

• New features, table.
• Updated collections.
• Keyboard shortcuts for the note tree.

🛠️ Technical updates

• Updated to Electron 37.2.2.
• Mindmap dependency (MindElixir) was updated to the latest major version.
• Mermaid diagrams updated to the latest version (new diagram type tree map supported).
• CKEditor updated to latest major version (46).

---

This discussion was created from the release v0.97.0.

[XavierFigari]

Great ! Thanks. Version number is still 0.96.0 though : I guess package.json needs to be updated ?
(I'm using the Docker image triliumnext/trilium:v0.97.0)

[eliandoran]

@XavierFigari , you're absolutely right. I'll take care of it.

[capi]

Will there be a 0.97.1 release to fix this, or will at some point the package / docker image be "fixed"?

[eliandoran]

@capi , the desktop builds have already been switched in-place.
But sure, I'll probably do a .1 later in the evening to have everything clean.

[diyoyo]

Thanks for this update!

Regarding the name of "Collection": I agree the name "Book" was mega confusing
That said, given the Table and the calendar way of handling things, and given the #projectOwnervalue (was it there before?), it looks more like a "Project" than a "Collection", imho.
Of course, calling it collection is a way to stay close to "Notes" semantically, but I foresee the viewType going more and more towards a multi-view made of all the current view types: so basically a project dashboard.

[eliandoran]

It will sure support multiple views per collection at some point but I personally prefer the term of Collections as opposed to a Project.

It immediately communicates to a new user what it is about: a set of notes grouped together.

Not sure about the #projectOwner label. Where did you see that?

[rom1dep]

@diyoyo : the idea behind Collections is to provide a way to view and interact with a large number of notes and their attributes, in one place (hence the name).

Those notes can be anything ranging from short text notes to complex hierarchies of template/relations-heavy typed notes with tons of attributes and relations. In the latter case, Collections should (and will increasingly over time) enable advanced workflows like the ones found in other PKMSs (often referred to as databases).

We can indeed now efficiently run whole "Projects" through Collections (managing a series of notes representing tasks with assignees, due dates displayed on a calendar, and soon, kanban boards, …), but Collections do help with more mundane tasks, like keeping track of your comic books library, track your fitness activities, collect places where to travel… in fact, any short or large set of notes can benefit from Collections, irrespective of the user's proficiency level with Trilium.

Re: #projectOwner that is news to me, where did you see it? (I grepped the codebase and didn't find anything).

[diyoyo]

ok, now I definitely agree with you both @eliandoran and @rom1dep .
And again, please accept my apologies for making quick statements. Fact is, I tried the table view on my "Project" template (where I actually had forgotten about the projectOwner attribute) ... but ... the weird part about it is that it made it look like the table randomly picked some attributes to put them into columns. In addition to title, columns are only ProjectOwner, startDate, startTime, endTime, endDate, and... Wikipedia, lol. At the same time, there are many more ownedAttribute and inheritedAttributed. At the end of the day, I didn't choose theses columns nor to give them higher priority than others. Hence the confusion.

[diyoyo]

Ok, I don't know where I read it already, maybe from the git commits: It's not random at all, it's just that only the "single" attributes are picked by the table.