🇵🇱Poland @gpietrzak

joevagyok → credited gpietrzak → .

joevagyok → credited gpietrzak → .

Hello, the work is still in progress, but I plan to finalize it soon.

gpietrzak → created an issue.

Maybe it is related to https://www.drupal.org/project/drupal/issues/3457061 🐛 Bootstrap Modal dialog Not closing after 10.3.0 Update Closed: works as designed core issue

This is the patch → to the latest 8.x-3.6 stable version

gpietrzak → created an issue.

Fixed in https://www.drupal.org/project/advanced_mautic_integration/issues/3448523 📌 Set up CI/CD pipelines Fixed

gpietrzak → created an issue.

Closing as duplicate of #3448360
Sorry, but the MR breaks most of the coding standards.
Only the JS file was not covered by CodeSniffer rules.

Thanks for contributing, however, the license should be GPL v2

Thanks for the great feedback! I've added all the remaining issues to the module backlog for easier tracking.

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue. See original summary → .

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue.

I can't give you the exact date, you can follow the progress on our GitHub
https://github.com/droptica/droopler
https://github.com/droptica/droopler_project

There is a drupal10 branch with the latest changes regarding D10

Yes, the new version will be released very soon

$variables['main_attributes'] is an object of the class Attribute, so you can't assign a string to it

You have to override the behavior of droopler_theme_preprocess_page(), by adding the class "container-fluid" to $variables['main_attributes']

There will be a new version soon that fixes it

There should be a stable version in the following weeks. There are no complications on Droopler side.

There is still geysir and we_megamenu (which is updated only on dev branch, without a release)

Hello, as far as I can remember this region is only used to put facets on the product list. It is not rendered on other pages (as it collides with full-width paragraphs).

If you wish to have it, you have to override the page template in your subtheme.

Hello, this module will be removed in Droopler 3.2. For now, Droopler 3.1 is not compatible with Drupal 10 for a lot of other reasons, so removing the module won't do any change.

Hello, Droopler 3.1 is not compatible with Drupal 10 yet, the compatibility will be a part of upcoming 3.2 version. We've got some work in progress, but it will take some time until we fully test it.

I updated the scope of the ticket, as we have more incompatible modules.

For now, we still wait for:

• drupal/config_update https://www.drupal.org/project/config_update/issues/3330880 💬 2.0.0 release w/ Drupal 10 support Fixed
• drupal/features https://www.drupal.org/project/features/issues/3297177 📌 Automated Drupal 10 compatibility fixes Fixed
• drupal/geysir https://www.drupal.org/project/geysir/issues/3297304 📌 Automated Drupal 10 compatibility fixes RTBC
• drupal/lazy https://www.drupal.org/project/lazy/issues/3297512 📌 Automated Drupal 10 compatibility fixes Fixed
• drupal/linkit https://www.drupal.org/project/linkit/issues/3288339 🐛 Drupal 10 compatibility Fixed
• drupal/we_megamenu https://www.drupal.org/project/we_megamenu/issues/3300703 📌 Drupal 10 readiness Fixed https://www.drupal.org/project/we_megamenu/issues/3299477 📌 Automated Drupal 10 compatibility fixes Closed: duplicate

gpietrzak → created an issue.

gpietrzak → created an issue.

gpietrzak → created an issue.

We will verify this and fix in 3.2 if possible

We started to create a backlog for D10, it will be a part of Droopler 3.2.0. We will update the modules and check the code. All the issues will be tracked on drupal.org.

The change will be a part of Droopler 3.2.0

The change will be in Droopler 3.2.0, along with other automated code checks

Hello, we are putting it in the queue for the 3.2 version

This URL is hardcoded in the route definition, so you should probably define a subscriber service - like here: https://drupalsun.com/philipnorton42/2022/10/16/drupal-9-altering-routes...

We've added the ticket to the v3.2 scope, the `search` module dependency will be removed.

Hello, currently, we are in the phase of planning Bootstrap 5 update. The problem here is that it will become incompatible with B4 installations.