Background: I am trying the test.logseq.com DB version. After import “File to DB graph”, I found that images are still keeping as  format in the node, and images can be display well. no problems.
Problem 1: When I try to export both DB graph and assets, the page show error “This page is having a problem”
Problem 2: Then I try to export the DB graph, and import the export DB graph as a new graph. I can see the image block’s content is still , but the image is not displayed.
I tried to copy the whole “assets/” folder in the same folder with export DB graph(db.sqlite), still cannot work.
Problem 3: I create a new DB graph, make a image Asset, and export both DB graph and assets successfully. I open a new graph with the export DB graph and the image still cannot be displayed.
Above problems prevent me from continuing to use logseq DB version. If there is any problem with the database version, even exporting the database graph backup does not resolve it, as images cannot be displayed. I have many images stored in the assets/ folder within the markdown graph.
Please help to check and provide advices how to backup and import assets correctly. Thank you!
Logseq DB is currently in alpha being tested with a group of testers.
Have you signed up for this tester group already?* Because the devs only monitor a specific GitHub repo at this moment for bug reports about DB, not this forum. The reason is that we’re a small team and can’t handle too much feedback at once.
*I expect the rest of the waiting list to be invited around end of February.
Hi @Ramses
Thank you for your reply!
I signed up but haven’t received an invitation yet.
After using DB version for 3 days, I discovered two more issues, so I’ve decided not to switch my primary graph to the DB version until they’re resolved:
The “Page Tags” property cannot be added to a block, but can be added to page.
When entering an existing page name in the “Page Tags” property, it always displays a new option instead of recognizing the existing one.
I need to link some existing pages into the property, similar to how the “tags” property functioned in the previous version.
There’s still a queue of ~800 people. We’ve invited about 600 testers so far, but we’re a small team and can’t handle too much feedback at once. That’s why we invite people in waves.
Logseq DB is not feature complete yet and is NOT suitable for primary use at this moment. So, it’s good that you made this decision, because one wipe of your browser cache (or some other instability) and your graph is gone. That’s why there’s an early (automated) backup feature in Logseq DB now, but that doesn’t mean it’s suitable for day-to-day use.
We strongly recommend against adopting Logseq DB as your main driver until it’s more stable and there are local apps. Only use Logseq DB for testing and if you can afford to lose your notes.
Thank you for reply! I only keep the DB version for testing now.
For “Page Tags,” I want to add [[page1]] as a property for a block, similar to add the “tags:: [[page1]]” property in the current version. How can I achieve this in the DB version?
You just need to tag your block, add a property (i.e. topics:: into your tag (i.e. #actionNote is my tag), define the Property Type (i.e. as node) and choose the desired value (i.e. Page 1 #topic ) .
