You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 0.22.5, when I delete an image, the image will be moved to Unused resources. But in v0.23, image seems disappeared after removed. I used to insert the attached imgs into the content and then remove them from attachments, I don't like images to be showed both in the article and in the attachment (redundant & very boring).
Steps to reproduce
N/A
The version of Memos you're using
0.23
Screenshots or additional context
No response
The text was updated successfully, but these errors were encountered:
The Unused resources section is where uploaded resources are listed that are waiting for their memo to be saved so they can be attached to the memo. If you end up not saving the memo or removing the resource before saving the memo the resources stay in the Unused resources section.
When you are removing resources from saved memos (these resources are not in the Unused resources section) by updating the memo, removing the image and saving, those resources are removed from your app completely. I was under the impression this has been the behaviour for a while and don't recall any changes to how deleted files work since v0.22.5. Change list.
Your way of uploading images and using their URLs to add them inline should still work as expected, just make sure you dont save the memo while the image is attached or it will be removed when you edit and remove in the future
Describe the bug
In version 0.22.5, when I delete an image, the image will be moved to Unused resources. But in v0.23, image seems disappeared after removed. I used to insert the attached imgs into the content and then remove them from attachments, I don't like images to be showed both in the article and in the attachment (redundant & very boring).
Steps to reproduce
N/A
The version of Memos you're using
0.23
Screenshots or additional context
No response
The text was updated successfully, but these errors were encountered: