Obsidian links to non-existant notes display as null in Foundry journal
kuchrk24 opened this issue · 4 comments
Yeah I'll need to add this scenario to the test vault so I don't break this in the future. Clearly unexpected behavior during the link conversion process.
At least as far as images go, if you use an S3 compatible service from anyone other than AW, the endpoint naming convention is different so the link points to the wrong place.
Currently, you hardcode s3
and amazonaws.com
in the link.
path = https://${settings.s3Bucket}.s3.${settings.s3Region}.amazonaws.com/${path}
;
For a service like DigitalOcean, their endpoint name is
https:\{s3Bucket}.{s3Region}.digitaloceanspaces.com
Kind of a pain to have to support multiple providers with different naming conventions.
@kuchrk24 are you able to reproduce this behavior on the latest version? I cannot. I think this was fixed along with several things.
@captaingoodnight I think the S3 issue got resolved via another ticket. I did not have the FilePicker
implemented incorrectly. So if you are able to use alternative services in your foundry config, it should work. Can you try this on the latest module version? Thanks!