-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after latest upgrade all my picture links are broken. #1988
Comments
hi, i fear it is my fault. I explained the problem here: #1941 (comment) as a current workaround: if you rename the folder "images" at your boostnote storage location to "attachments" it might work again (see the comment linked above for the explanation) |
so after the latest updates all new pictures are working but all previous ones are still broken. all broken pages have a double file://file:// reference. is this a fixable thing or must I just forget about the screenshots? |
@dogfish182 have you solved your problem? |
@ZeroX-DG I have the same problem. After upgrading to 0.11.13 all image links are broken. Steps to reproduceUpgrade to latest version and check image preview or try to add a new image. Enviroment
|
Same problem as @XarisA ; any image paste turns as a broken image (still visible in folder though) Edit: also same for any previously added image |
Current behavior
for some reason after upgrade all the pictures are referencing an 'attachments' directory. this directory is empty and all images are stored in an images directory.
I guess I can manually move them back, but this seems worth reporting.
all the broken links refer to the 'attachments' path
but all images are contained now under the 'images' dir.
I see this running all through developer mode as well
Attachment folder ('/Users/me/onedrive/OneDrive -Me/Boostnote/attachments/76e76858-f85a-4075-866a-712bafefe06d') did not exist..
Expected behavior
pictures should work after upgrade
Steps to reproduce
upgrade to 11.5. have broken images.
Environment
The text was updated successfully, but these errors were encountered: