Images not found
Search first
- [X] I searched and no similar issues were found
What Happened?
All of my images are gone today.
Reproduce the Bug
I do not understand this instruction.
Expected Behavior
Please retrieve them.
Screenshots
Desktop or Mobile Platform Information
App Version: 0.9.18 Git Revision: 6eb82e8 Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.9.18 Chrome/112.0.5615.204 Electron/24.6.3 Safari/537.36 Language: ko Plugins: logseq-block-calendar (v0.2.8), logseq-todo-plugin (v1.19.0), logseq-journals-calendar (v0.10.10), logseq-awesome-styler (v3.7.1), logseq-bullet-threading (v1.1.1), logseq-banners-plugin (v3.4.11), logseq-plugin-gpt3-openai (v1.13.1), logseq-helium-plugin (v.2.1.3), logseq-emoji-picker-fork (v0.0.5), unfinished-business (0.1.6), logseq-toolbox (0.0.3), logseq-unsplash (v1.0.0), logseq-tags (v0.1.2)
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
Could you post the source markdown of the block?
p{margin-top:0;margin-bottom:0}
I got all imaves back now. I deleted images from the Gallery on the phone, and that caused the problem.I retrieved from the bin and got them back all.But one thing that I still don't underatand is that why images are not stored in asset file?Thank you.---- 원본 메일 ----보낸 사람 : ***@***.***>받는 사람 : ***@***.***>참조 : ***@***.***>, ***@***.***>날짜 : 23.10.04 04:07 GMT +0900제목 : Re: [logseq/logseq] Images not found (Issue #10308)
Could you post the source markdown of the block?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.> [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/logseq/logseq/issues/10308#issuecomment-1745562241", "url": "https://github.com/logseq/logseq/issues/10308#issuecomment-1745562241", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
It should be copied. Could you provide the raw markdown source?
p{margin-top:0;margin-bottom:0}
What is raw markdown source of the block?---- 원본 메일 ----보낸 사람 : ***@***.***>받는 사람 : ***@***.***>참조 : ***@***.***>, ***@***.***>날짜 : 23.10.04 04:07제목 : Re: [logseq/logseq] Images not found (Issue #10308)
Could you post the source markdown of the block?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.> [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/logseq/logseq/issues/10308#issuecomment-1745562241", "url": "https://github.com/logseq/logseq/issues/10308#issuecomment-1745562241", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Hi There! 👋
We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!
If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.
Access additional Logseq 🚀 resources:
- Forum: https://discuss.logseq.com
- Blog: https://blog.logseq.com
- Docs: https://docs.logseq.com
Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!