-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
关系图点击标签节点报错 #7176
Comments
Please try again after rebuilding the index, if that doesn't work, please wait until the next version is released, we are improving the data index. |
Thanks D for your fast reply! Rebuilding the index did not resolve the issue for me so I'll wait for the next release with improved indexing and retry |
@Vanessa219 @88250 Maybe this is something for frontend development so ensure that clicked "tag" nodes will open the tag search window instead of trying to open a block. In the current version (2.7.3) the behaviour can simply be reproduced by opening a blank page, adding some Maybe you could disable any UI actions when the graph tag node is clicked or open the search window (so the the same action will be triggered as clicking a text block embedded |
该问题是否已经被报告过了? Is there an existing issue for this?
I have searched the existing issues
该问题是否能够在默认主题(daylight/midnight)下重现? Can the issue be reproduced with the default theme (daylight/midnight)?
I was able to reproduce the issue with the default theme
描述问题 Describe the problem
SiYuan User Guide
Global Graph
node map and set the following display optionsNote
tag in the Global Graphtag
nodes results in an error that the block id is unknown期待的结果 Expected result
Clicking on a
tag
node in Global Graph should open the search window displaying all blocks where thetag
had been found like using the editor.截屏或者录屏演示 Screenshot or screen recording presentation
Display options used for Global Graph
Error message when clicking a
tag
nodeExample (Expected behaviour when #Content Block# node was clicked)
版本环境 Version environment
日志文件 Log file
更多信息 More information
No response
The text was updated successfully, but these errors were encountered: