D

It is recommended to disable all plugins and code snippets, switch to the default theme, and then observe the results.

Please log out and log back in, then observe the situation. Thank you.

Thanks for clarifying. Please contact us at [email protected] for assistance with the invoice. Please include your PayPal transaction ID and the billing information required for accounting purposes. Do not post this information publicly. Thank you.

Hello, your account benefits have been automatically activated after purchasing PRO Features.

Ref Issue #18899 · siyuan-note/siyuan

There are currently no development plans for task management; it is recommended to look for relevant plugins in the marketplace.

As far as I know, there aren't any free APIs available, but you could try looking around for one.

The AI agent has access to all data, except for closed encrypted notebooks. Therefore, if there is any data you do not want the agent to access, place it in an encrypted notebook and close that notebook.

Try adding an exception in your antivirus software.

This has been fixed. When a document is loaded, content blocks placed directly under a list will now be automatically wrapped in list items and saved. This is not limited to paragraphs. The fix will be included in the next version. Thank you for the detailed report.

Thank you for providing the detailed information.

The specific problem is that a NodeParagraph was stored directly under a NodeList. A valid list structure should be NodeList - NodeListItem - NodeParagraph. A paragraph inside a list item is valid.

This invalid structure already existed in the document before upgrading to v3.8.0. v3.8.0 added transaction structure validation to prevent additional invalid data from being written. When an edit affects this invalid list, the transaction is rejected and the interface reloads. The “Allow creating sub-documents deeper than 7 levels” setting is unrelated to content block structure. Exporting and reimporting the workspace also preserves the invalid structure, so it does not resolve the problem.

Please back up the workspace first, and then try restoring the affected document through Data History.

The database failing to open in v3.7.3 is a separate issue. After a database is saved by v3.8.0, its Attribute View data format is upgraded from spec 5 to spec 7, which v3.7.3 cannot read. The database does not need to have been originally created by the newer version, so the current message saying it was “created by a newer version” is inaccurate. It actually means that the database was last saved using a newer data format. Please avoid switching versions repeatedly within the same workspace.

Hello, we do not currently have any hiring plans.

You can currently access the site without registering. If you do choose to register, you can only use a mobile phone number from mainland China.

There is indeed an issue with this at the moment; let's just leave it aside for now. :)

In the next release, we will continue to improve the timeout implementation and add a Stream Idle Timeout parameter. If convenient, you can build from the dev branch to participate in testing, or wait until we release v3.7.3-alpha.1. Thank you.

Please export and upload the SiYuan system logs zip.

Thank you for the feedback. Please check again after the next version is released. Thanks.

The "verify AES key failed" log entry indicates that your data vault key is incorrect; please refer to the "Lost Key" section in the User Guide FAQ to resolve this.

It is important to note that all devices must reset their data repos and use the same key, and a new cloud storage directory must be used instead of the old one.

For example, set it to D:\SiYuan\

As far as I know, only PlantUML renders online by default; however, you can configure it in the settings to use a local rendering service instead.

Please export and upload the system logs from Settings > About so that we can assist you in diagnosing the issue.

Currently, opening PDFs is not supported on mobile devices. Support may be added in the future; please follow Issue #10911 · siyuan-note/siyuan for updates.

My test results are always on the left:

Since the API can be invoked directly via the command line, we do not believe there is a significant need to provide a separate command-line interface.

While SiYuan already provides a powerful API, an official CLI would make these workflows much more accessible and convenient.

Could you give an example?

The table will not be adjusted for the time being; the link embed are also not planned to be implemented, as previously considered (in Chinese Issue #1020 · siyuan-note/siyuan ), it seems there's a plugin that can achieve this.

Thank you.

It seems more reasonable to place the currency symbol at the beginning, as we have observed with Notion.

The Select field can only use text, adding other value types is not being considered.

Perhaps an Asset field would be more suitable for your situation.

This vulnerability will be fixed in the next version (v3.5.5).

PS: All disclosed security vulnerabilities and their fixes can be found here:

Build software better, together GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects. GitHub - github.com

Simply deleting the text from the database will restore the dynamic anchor text.