url filter returns invalid attachment URLs in flow blocks when alternatives used

[eigengrau]

When a flow block has a field referencing a page attachment…

[field.image]
source = record.attachments.images

… and when a non-primary alternative of a page is being generated, the expression {{ this.image | url }} inside the flow block template will yield a URL within the alternative prefix, which leads to a 404.

As a work-around, {{ this.image | url(alt='_primary') }} will lead to the desired URL.

[dwt]

I'd like to add that on 3.2 I also see this happening in content markdown. I have markdown like this:

![](martin.jpg)

Which renders then renders the alternative prefix in the path to the image - which of course renders wrong.

My workaround was to write the absolute path of the image down in the translation - which is of course not pretty.

![](/about/martin.jpg)

I think that relative paths in markdown should still link to the correct image. Either because it is re-generated at the new location (perhaps as a sym- or hard-link) or because the link is fixed to point to the original file.

[dwt]

Also See #313