The blazy module's implementation of hook_blazy_settings_alter() incorrectly assumes that every blazy rendering while a Views view is executing should have the current view mode set to the View's display id.
Example: A view can be configured to render nodes in a selected view mode, and any image or media fields on the node should render the blazy formatters in the view mode for that entity display config, not the view's display id.
Method in "\Drupal\blazy\BlazyAlter":
/**
* Implements hook_blazy_settings_alter().
*/
public static function blazySettingsAlter(array &$build, $items) {
$settings = &$build['settings'];
// Sniffs for Views to allow block__no_wrapper, views_no_wrapper, etc.
if (function_exists('views_get_current_view') && $view = views_get_current_view()) {
$settings['view_name'] = $view->storage->id();
$settings['current_view_mode'] = $view->current_display;
$settings['view_plugin_id'] = empty($settings['view_plugin_id']) ? $view->style_plugin->getPluginId() : $settings['view_plugin_id'];
}
}
Build a page with a view that using a "Rendered entity" field in a specific view mode.
Remove blazy_blazy_settings_alter()
OR
Determine a better way to set the 'current_view_mode' when rendering a single views field with a blazy formatter.
Fixed
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since #3257511: Optimization pre Blazy 3 → , I changed a lot to separate configurable vs non-configurable settings to avoid the collisions.
Feel free to re-open if still an issue. Be sure to detail more for a repro.
Thanks
Automatically closed - issue fixed for 2 weeks with no activity.