Een hart voor de Drupal Community

Bij make it fly geloven we sterk in Drupal en Open Source software in het algemeen. We maken dagelijks gebruik van vele open source componenten en de vele Drupal modules die beschikbaar zijn. We dragen actief ons steentje bij aan de community door zelf patches, modules en documentatie te voorzien, daarnaast zijn enkele teamleden ook actief in de Drupal User Group vzw.

Een overzicht van onze bijdragen aan de Drupal community vind je terug op onze Drupal.org pagina. Naast het actief meerwerken aan de Drupal community, zetten we ook andere ontwikkelaars op weg door vragen te beantwoorden op Drupal Answers.

  1. The website encountered an unexpected error. Try again later. TypeError: implode(): Argument #1 ($array) must be of type array, string given in implode() (line 74 of modules/contrib/layout_builder_iframe_modal/src/Form/LayoutBuilderIframeModalSettingsFor

    Sven Decabooter
    Sven Decabooter added a comment on drupal.org: The website encountered an unexpected error. Try again later. TypeError: implode(): Argument #1 ($array) must be of type array, string given in implode() (line 74 of modules/contrib/layout_builder_iframe_modal/src/Form/LayoutBuilderIframeModalSettingsFor
  2. The website encountered an unexpected error. Try again later. TypeError: implode(): Argument #1 ($array) must be of type array, string given in implode() (line 74 of modules/contrib/layout_builder_iframe_modal/src/Form/LayoutBuilderIframeModalSettingsFor

    Sven Decabooter
  3. The website encountered an unexpected error. Try again later. TypeError: implode(): Argument #1 ($array) must be of type array, string given in implode() (line 74 of modules/contrib/layout_builder_iframe_modal/src/Form/LayoutBuilderIframeModalSettingsFor

    Sven Decabooter
    Sven Decabooter added a comment on drupal.org: The website encountered an unexpected error. Try again later. TypeError: implode(): Argument #1 ($array) must be of type array, string given in implode() (line 74 of modules/contrib/layout_builder_iframe_modal/src/Form/LayoutBuilderIframeModalSettingsFor
  4. Make compatible with 'Administer users by role' module

    Sven Decabooter

    Improved the logic from #3451443: Add permission for resending emails to make it compatible with other modules, that provide a workaround for the broad 'administer users' permission. Now you can access the feature when you have 'administer users' permission, or the module-specific permission.

  5. Add permission for resending emails

    Sven Decabooter

    Added the new permission, while keeping the existing access logic intact. You can now use this functionality if you are able to update user entities (current access logic), OR apply the action to user entities if you have the newly added permission granted.

  6. Troubleshooting this module?

    Sven Decabooter

    I guess you would need to debug this via XDebug or something... Alternatively, you could switch to using the Drupal Symfony Mailer Plus module with an SMTP transport configured, and install Drupal Symfony Mailer Log module. This will create a log entry for each outgoing email, making it easier to debug if the mail is going out or not.

  7. Resend email, if user has not confirmed account for X days

    Sven Decabooter

    Sorry for not coming back to this. That seems like a useful feature to be added to an optional submodule, for users seeking that functionality. Or within the module itself as a configuration option (but disabled by default).

  8. Flushing image, when webp module is used, doesnt work correctly

    Brecht Ceyssens

    The combination of these 2 tickets causes issues:

    • https://www.drupal.org/project/flush_single_image/issues/3187232
    • https://www.drupal.org/project/flush_single_image/issues/3102639

    When the webp image exists, it will only delete that one causing images but the be updated correcly. If you choose regeneration, the derivative is forced saved as the webp variation.

  9. Core 11.2^ support - Refactor widgets

    Sven Decabooter

    I tested this logic, both updating fields created in the 3.x version, and adding new fields. I have found no real issues with it. Seems like a good improvement to me.

  10. Add a cleanup function

    Sven Decabooter

    OK those seem like 2 valid points to stick with the current approach. If the current logic would pose unexpected problems, we can still change the implementation later on.

Sven Decabooter - Drupal Developer

"Onze teamleden bouwen zelf ook mee aan ons geliefde Drupal, en daar zijn we trots op"

Sven Decabooter
Drupal developer

Betrouwbare technologie, naadloze prestaties. Dat zijn onze Drupal-oplossingen.