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
When a urlPath option is NOT provided to the transform plugin, but the template including the image has a permalink attribute that is a filename, not a directory, the image source is incorrectly uses the full html path as if it was a directory. For example:
I'd expect it to understand that the permalink is the full path to the file in this case, not a directory with an index file. This should result in the following (which correctly links to the file):
Repro here: https://github.com/nathonius/11ty-demo/tree/main/4-images
Discord thread about this issue
When a
urlPath
option is NOT provided to the transform plugin, but the template including the image has apermalink
attribute that is a filename, not a directory, the image source is incorrectly uses the full html path as if it was a directory. For example:/blog/posts/Blog Post.md
results in
I'd expect it to understand that the permalink is the full path to the file in this case, not a directory with an index file. This should result in the following (which correctly links to the file):
Either removing the permalink (or using a directory permalink) or using a
urlPath
in the plugin config bypasses the issue.The text was updated successfully, but these errors were encountered: