Search first
What Happened?
I migrated from OG to DB only to find all my embedded asset alt texts had not survived the migration
Reproduce the Bug
- In Logseq OG 1.0.0
- Add new graph "Temp"
- Create new page "This Is the Page Name"
- Add file "this-is-the-file-name.pdf" to page
- Edit alt text (see screenshot)
- From "this-is-the-file-name.pdf"
- To "This is the alt text"
- In Logseq 2.0.1
- "Import existing notes" → "File to DB graph"
- Select Temp graph from step 1.1
- Select "Submit" to import
- Navigate to page This Is the Page Name
Expected Behavior
On the page imported from OG to DB, the alt text is completely gone (see screenshot), replaced by the asset name.
When importing, could the asset name be set to the alt text instead of the file name?
I don't want to lose the alt next on all my assets when migrating to Logseq DB
Screenshots
In Logseq OG
In Logseq DB
Files
No response
Browser, Desktop or Mobile Platform Information
OS: Kubuntu 26.04
Source: Desktop Logseq OG 1.0.0 (revision 680b371)
Destination: Desktop Logseq 2.0.1 (revision b09316a)
Additional Context
Installed plugins:
- Bullet Threading
- Journals calendar
Result is the same with these plugins disabled
Dev tools console has no errors
Are you willing to submit a PR? If you know how to fix the bug.
Search first
What Happened?
I migrated from OG to DB only to find all my embedded asset alt texts had not survived the migration
Reproduce the Bug
Expected Behavior
On the page imported from OG to DB, the alt text is completely gone (see screenshot), replaced by the asset name.
When importing, could the asset name be set to the alt text instead of the file name?
I don't want to lose the alt next on all my assets when migrating to Logseq DB
Screenshots
In Logseq OG
In Logseq DB
Files
No response
Browser, Desktop or Mobile Platform Information
OS: Kubuntu 26.04
Source: Desktop Logseq OG 1.0.0 (revision 680b371)
Destination: Desktop Logseq 2.0.1 (revision b09316a)
Additional Context
Installed plugins:
Result is the same with these plugins disabled
Dev tools console has no errors
Are you willing to submit a PR? If you know how to fix the bug.