Could you be more elaborative? Graph view currently as I use is limited, but clicking each node does open that document which is linked. I have no knowledge of possible graph specific plugins/extensions from marketplace to exand graph features.

Im not sure i read your post as intended.

I use backlinks to database in a specific way that might differ from yours. The primary key in the database can link to any block type, then the entry row's primary key cell can be hovered over to take you to that block. That block also also has a link you can hover over that takes you to that primary key cell.

I havent check how the graph for specifically that linkage/database-relationship.

Hi, your firewall response prompted my interest, can i ask your experience with firewalling siyuan?

1. Does your firewall constraint/block rules to contain siyuan have edge cases, since siyuan might open temporary/arbitrary ports. Linux, for example, can grant any application additional free-to-use temporary ports alongside predetermined ports for siyuan like 6806?
2. Which firewall do you have best experience isolating the network access for siyuan?
3. Have you encountered edge cases, tested with network isolation on siyuan and tips you can share which you do to succession?

I placed my workspace anywhere i wish without any issues ever. Though i do not use cloud syncing and designating local folders as a cloud context, but that is exactly what the Siyuan warning you mentioned is about, since any cloud service can maintain folders and do unexpected edits to folders (and its structure) as part of the service which could cause issues for Siyuan. Siyuan should retain sole ownership of the folder to function.

I have been using Siyuan for a long while. Obsidian I have used far less. I do find Siyuan superior and havent regretted or had any desire to switch back to obsidian. If you do commit to migration to siyuan from obsidian, obviously there isnt an ideal back and forth migration (between siy vs obs) that retains all document structures, backlinks perfectly intact last I tested 6 months back, mainly because the syntaxes differ (and features differ) between the two apps for creating backlinks. I have seen some third-party tools specific to migration, and since 6 months there might be better solutions I havent figured out

Siyuan Excels in:

• editing: where Obsidian can still be a little quirky, rather Siyuan has flawless consistency editing paragraphs, code block, lists, embedded blocks and not to forget moving any block types around. Moving blocks and nesting blocks also feels superior in Siyuan
• Backup/restore: Siyuan can backup of entire workspace, partial documents, migrate to new workspaces while retaining prior structures and context flawlessly. I havent had any issues starting anew, creating temporary workspaces. I have less understanding how Obsidian deals with deep backup/restore that much, but Siyuan wont leave you hanging or yurning obsidian.

There is more to be said and compare, but basically, Siyuan never left me hanging or desiring a switch. The core features of siyuan (some mentioned above) as stable PKM were superior, where Obsidian (and switching between edit view vs reading view) seems more quirky.

Thank you for the clear annotation of the problem.

More users with prior invalid structures before 3.8.0 will encounter the issue of structure validation when they upgrade to 3.8.0. Before 3.8.0 there was no validation, but 3.8.0 introduced validation, which is good to have, but the feature was introduced without addressing edge case which I encountered, without clear error message or instructions for course of action. At minimum a reference to e.g. NodeParagraph [20250516075716-d9nsrjg] would have provided a clear course of action to resolving the issue. siyuan.log is currently the only indication provided.

Then regarding your advise to back-up and restore through data history would be very tedious: imagine if the invalid structure was months back or years back when siyuan was first used, and a long time later 3.8.0 was the trigger with its validation.

My preferred action was: 1. inspect siyuan.log, copy affected paragraph backlink, paste anywhere and a click takes me directly to the paragraph for me to delete

Possible solutions:

1. Minimum action: error message referencing the affected backlink NodeParagraph [20250516075716-d9nsrjg]
2. Average action: error message bullet 1 + basic instruction to user: backlink 20250516075716-d9nsrjg will take you to affected paragraph to manually delete the culprit paragraph
3. Another average action: similar approach to Settings -> Assets -> Unreferenced {assets,database,Missing_assets} include a broken_backlinks where all affected paragraphs are gathered and organized, after an initial scan/health check when 3.8.0 is first installed.
4. Best action: Siyuan automatically handles each and every paragraph by turning the paragraph into a arbitrary valid structure siyuan 3.8.0 validation expects: NodeList - NodeListItem - NodeParagraph or delete it if empty paragraph like in both my example images (which were empty).

I don't expect it to be easy to implements solutions to edge cases, please view my contribution as suggestions, otherwise edge case users are left unanswered, invalid paragraphs also linger and corrupt any back-up or data history which accumulates, and let me remind you that it is very easy to by mistake press accidental Enter without realizing it resulted in invalid paragraph/structure failure.

Please assist and help with the issue i am stuck in version 3.8.0, cant revert to 3.7.3, because both ways something breaks, either the list or the databases

I do not think the issue is caused by siyuan as the program itself. Since you cannot acces workspace for creating a backup, try to backup the entire siyuan workspace directory to an external USB to restore later.

1. For testing download try the siyuan .deb format instead of the AppImage, see if issue persists.
2. If you have a Virtual Machine, try siyuan inside the guest OS to see if same issue persists. Alternatively another device/laptop entirely for testing.
3. Try system update sudo zypper dup for example
4. Try checking if your diskspace is full. Tools like qdirstat will allow you to check diskspace using GUI, instead of terminal. The error refers to cloud storage, probably because there is no diskspace.
5. In worst case scenario OpenSUSE allows to revert to a snapshot. You should try that

Better solution i think:

1. Create block
2. Copy reference
3. Paste in new page
4. Right click "purple reference" and select Turn into-> Define Block and its children

Step 4 will move original block to destination note and place the reference of original in source note. Basically switch original and reference positions.

Any network packets when auto update, Google analytics, upload errors & diagnostics and Network serving are disabled?

No response yet? I have the same issue and found solution 2 worked for me. Try option 3 first then 2.
Troubleshoot in english is difficult to find. I checked the chinese github issues for you and translated with links:

1. Usefull to remember there are two log files (Source: https://github.com/siyuan-note/siyuan/issues/8047):

   • log 1: Workspace--> /temp/siyuan.log
   • log 2: C:\Users\username.config\siyuan\app.log (windows) OR /home/User/.config/siyuan (linux)

2. Delete the folder in C:\Users\username.config\siyuan(windows) or /home/user/.config/siyuan(linux ) Before deleting try disabling anti-virus and firewall if possible (Source: Issue #8047 · siyuan-note/siyuan)

   This forces you to relocate your workspace to open

3. Kill the SiYuan-Kernel process in task manager and restart:
   Source: Issue #8047 · siyuan-note/siyuan

I appreciate your resonse, but it is not only for complete batch export for users to turn away from siyuan, but rather for collaborative reasons and to publish notes. Users of Siyuan can collaborate and share specific notes.

I just want a guide on how to use anchor hash. How would I proceed after I used the feature after export, so post anchor hash. I do not quite understand what to do with the new file after export.

I think the issue remains with anchor hash for the reason that it is limited to notebook currently, meaning I cannot select rendering from Markdown to HTML from the notebook_ex > export > (selectable=Markdown/siyuan.sy.zip).

How would i export my notes to HTML with anchor hash? I think I would be limited to using pandoc input.md -o output.html, I tried it with pandoc, which succesfully creates html with link to other note, but it just opens the other note without navigation to the <span> block, so no hash jump in browser (brave/firefox) to block.

The anchor hash feature currently creates a span object <span id="20231110120736-ze6m41f"></span>. Some kind of program should be able to understand and find this block inside the note as reference. Can anyone help me understand how this can be useful after export, where do I use this, which program understands this syntax?

The export mode Anchor hash for notebook Markdown exporting has some limitations.

In the case i want to publish a particular note (with links to other notes) my approach is:

1. From main notebook export the notebook you want to publish to .sy.zip file
2. Create new (temporary) notebook
3. import .sy.zip file to new temp notebook
4. Export temp notebook export it to any selectable format (only markdown is currently selectable)

Other limitation of Anchor has export and the only way I got it to work (performed testing by exporting to Obsidian):

• currently only works for notebook and does not allow nested notes. In the process of exporting all notes must be unnested inside notebook for .md export to function.
• Currently does not support block reference. Can only link to main note. Tested by importing to obsidian (not a siyuan issue, but a markdown syntax limitation i presume)

Depending on the responses here I might add a feature request soon that involves the concept of user selectable export syntax. In which before execution of export using anchor hash a user can type in the conversion syntax to apply. User is presented with input fields much like the settings > Export > Anchor text wrapping symbol fields.

Conversion syntax for siyuan > obsidian would be: [[test3.md/Note 2#^d8bf62|Note 2]] and conversion input fields could somehow be [[ .. / .. #^ .. | .. ]]

I noticed an issue with footnote mode posted Any export method not working (crash/freeze) app on setting -> Export -> Ref -> footnote