- 🇬🇧United Kingdom Alina Basarabeanu
Patch from #14 fixed the issue on Drupal Drupal Version 9.5.10 and entity_print 2.x-dev@dev.
Currently, issue 2860122 doesn't include an option to optimize CSS.
I am running into an issue that may be considered a bug.
If you have s3fs enabled but you did not enable the css_aggregation and the corresponding redirects necessary to make css_aggregation work with s3fs then the print will f$config->get('force_download')ail causing an error :
file_get_contents(https://example.com/s3fs-css/css/css_uw1Zc3jXzLr2tejqtnrdS4uPG5H-K56kKb9... not found.
That's because entity_print is trying to get the aggregated css file from /s3fs-css which is supposed to redirect to s3 if it's been set up to do so: https://cgit.drupalcode.org/s3fs/tree/README.txt?h=8.x-3.x#n134
However, I don't have the css_aggregation set up nor do I have it css_aggregation using s3 yet entity_print tries to do that and assumes optimize css will succeed.
Proposed Solution:
- Allow users to choose whether to optimize css.
Patch attached.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Patch from #14 fixed the issue on Drupal Drupal Version 9.5.10 and entity_print 2.x-dev@dev.
Currently, issue 2860122 doesn't include an option to optimize CSS.