Account created on 10 October 2005, over 19 years ago
#

Recent comments

🇩🇪Germany scroogie

This is a bit confusing indeed. The module provides a formatter for direct image fields (file fields), not for entity reference fields directly. The normal "Media" fields you see in Drupal, are nowadays entity reference fields.

So to get the functionality, you need to set the display type of the media type (not entity type) first. Go to

/admin/structure/media

and there on the manage display tab of a type with an image field, e.g.

/admin/structure/media/manage/image/display

for the builtin image type. There you can set "Dynamic Responsive Image" as the image formatter for the display type (of which you can create custom ones with Display Suite).

If you now configure the display of an entity type with a media (reference) field, you can choose this display type on the field.

🇩🇪Germany scroogie

Okay, I think I found out what the problem is, and it could actually be a bug, not a support request.

In the meantime I had installed imagewidget_crop for a different entity type, where I want users to crop manually. This seems to completely stop the generation of new imagestyles by drimage_improved. So I inadvertantly hit one of the options that removes / resets all drimage styles, and the module couldn't generate new ones because imagewidget_crop was installed.

As soon as I uninstalled imagewidget_crop, it worked again. Is this on purpose?

🇩🇪Germany scroogie

Sorry, to be more precise, it's only the "mini pager". The full pager works as expected.

🇩🇪Germany scroogie

I just found this issue so it seems to be related to vartheme_bs5:

https://www.drupal.org/project/vartheme_bs5/issues/3490701 🐛 "InvalidArgumentException: $string ("1") must be a string" in views Active

🇩🇪Germany scroogie

By the way, it works for me for other components from the organisms folder, but not with the navbar-brand molecure. Did I misunderstand something?

🇩🇪Germany scroogie

I encountered exactly the same issue with the same component navbar-brand. I use the replaces in the component file and added the line in webpack config, but both versions get included. What did we miss?
@duntuk, did you ever solve this?

Greetings

🇩🇪Germany scroogie

Did you manage to do this in any way? I'd be interested as well. For example an optional checkmark for "open end".

🇩🇪Germany scroogie

Okay, I found out that the footer color is set in the page-footer organism inside the components. While it uses $primary, it's not recompiled if I don't override it, so it stays the shaded original $primary color. That makes sense.

However, following the guide in https://docs.varbase.vardot.com/10.0.x/developers/theme-development-with... I'm not able to override it.

I copied the organism folder, added replaces: 'varbase_components:footer' in the page-footer.component.yml and uncommented the corresponding line in webpack.config.components.js. However, even if I hardcode values in that component, they don't take effect, no matter how often I run yarn components:build or yarn theme:full-build or whatever.

Does anyone have any idea what else I could try?

Production build 0.71.5 2024