possibri → created an issue.
Tested #10 and that looks to have fixed the error. Having people test it now, but upon initial checks things seem to work as expected. Thanks @tgauges!
I, too, am having this issue with the 2.0 version of the module, on Drupal 10.2.3, steps I've taken:
- Enable module and _responsive submodule
- Set up the Image Pipeline, set only WebP derivative in the pipeline
- Set that pipeline as the sitewide default
- Set the default sitewide pipeline for image style I'm testing with, since nothing was generated until I did that
- Flushed the style being targeted to recreate derivatives
- Confirmed .webp files in the specific image style directory I'm focusing on
- Confirmed image style is correctly set in view's field settings for the particular images/view I'm looking at
- Run a cache rebuild for good measure
- Refresh the page with targeted image, but I'm still seeing the original .jpg file as the img src
The readme.md file doesn't provide any additional instructions, but I'm wondering if there is some other config/modification we need to do in our theme to make sure it points at the webp (when supported by the browser) instead of the jpg?
I think this issue is related to this one: https://www.drupal.org/project/drupal/issues/2772523 🐛 Entity Reference Views Limit not working Needs work
Apparently for entity reference views the result count is hardcoded to 10, and ignores the "specified number of items" setting. The offset functionality still works though.
Came across this pair of errors today on a Drupal 9.5.9 install and wanted to shed more light on when these errors were triggered and how I stopped them with no patches.
1. Create a view and configure a block with contextual filter (user/author of content to display, in my case).
2. Add this block to the user "view" page using Layout Builder
3. Load user page without issue
4. Add a page to the existing view with a path wildcard
5. Saving view triggers preg_match error and when trying to load user page and get the "parameter 'arg_0'" error with WSOD.
6. Changing how the dynamic value is found between user from route or raw value from URL (in contextual filter settings) does not fix anything, but removing the wildcard from the path fixes the errors temporarily
The fix was to remove the block from Layout Builder and then add back the dynamic path to the page. Luckily I don't need the block, but the block seems to be fully out of commission now, as I cannot add it back to the Layout Builder view and trying to silently triggers the preg_match error.
So it makes me wonder, even though the error is indeed a deprecation in preg_match, why is the second parameter empty? This block was working just fine before I added the page to the view, and the dynamic page is also working fine once I removed the block, so it seems there might be some other strange behavior taking place? Still pretty new to all the changes from D7, so hopefully this is helpful.