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
Let's talk about how / whether we want to support images and image styles.
Images should just work, as they aren't conceptually that different to private files.
Current challenge with image styles
When rendering an actual image style, styles prefix the URL like the following: encryption://styles/$image_style/$schema/test/$destination/file.jpg
This leads to a couple of issues:
Maybe our entire approach to put the encryption profile into the path is broken.
An alternative could be to register one scheme per configured encryption profile:
encrypt_test
encrypt_aes2
Then every existing path based logic will simply work without any further workaround. One tricky question will be, is it actually possible to provide dynamic file schemes.
Let's talk about how / whether we want to support images and image styles.
Images should just work, as they aren't conceptually that different to private files.
Current challenge with image styles
When rendering an actual image style, styles prefix the URL like the following:
encryption://styles/$image_style/$schema/test/$destination/file.jpg
This leads to a couple of issues:
\Drupal\image\PathProcessor\PathProcessorImageStyles
The text was updated successfully, but these errors were encountered: