[META] Priorities & next tasks - Droopler 3.x and 5.x

Maybe it's worth adding the update of the frontend_editing module to 2.0.0-alpha2 to the package?

Next tasks

1. 📌 [META] Droopler 3.x and Drupal 11 Active
2. 🐛 Updating Project Browser to version 2.0.0-alpha9 causes a critical error Active
3. 🐛 In Droopler the Gin cannot see the second tabs Active
4. 📌 New theme (colors) for Droopler 5.x Active
5. 🌱 Automated testing - Research Active
6. 🐛 Frontend editing sometimes fails to update the page Active
7. 🐛 Tiles gallery / Sidebar tiles - Colorbox does not display the image on the first attempt Active
8. 🐛 Tiles gallery - “feature image” option does not work Active
9. 🐛 The /search/node page is not working. Active

Next tasks

1. 📌 New theme (colors) for Droopler 5.x Active
2. 🐛 Errors when changing the default home page from /welcome to another. Active
3. 🌱 Automated testing - Research Active
4. 🐛 Frontend editing sometimes fails to update the page Active
5. 🐛 Tiles gallery / Sidebar tiles - Colorbox does not display the image on the first attempt Active
6. 🐛 Tiles gallery - “feature image” option does not work Active
7. 🐛 The /search/node page is not working. Active
8. 📌 drupal/ala - has now D11 release - change code in composer.json Active

Done

1. 📌 [META] Droopler 3.x and Drupal 11 Active
2. 🐛 Updating Project Browser to version 2.0.0-alpha9 causes a critical error Active
3. 🐛 In Droopler the Gin cannot see the second tabs Active

I have 2 projects running on Drupal 10.x and noticing that Droopler 3.3.0 is now marked as unsupported I updated them to Droopler 3.4.4 which, to my surprise, is also marked as unsupported and not available to download anymore. So I looked into 3.5.x to continue the migration path and even though the description says "Droopler installation profile for Drupal 10." in composer.json, it works only for "drupal/core": "^11.0" and up.

From Drupal core release schedule → , we can see that : Drupal 10 will reach end of life mid-late 2026, when Drupal 12 is released. The exact date is not yet set.

For sites not ready to go on Drupal 11 just yet, I wonder if it would be possible to keep a Drupal 10 version of Droopler marked as supported?

Thank you all for your hard work on Droopler!

Thank you for reporting this :)
We will fix it in 1-2 weeks.

@leducdubleuet, changed the settings and it should mark Droopler 3.3 as supported now :)

Next tasks

1. 🌱 Automated testing - Research Active
2. 🐛 Restore view of "Add Paragraph" Active
3. 🐛 Misaligned divider in banner section Active
4. 🐛 Improve spacing in paragraphs Active
5. 🐛 User account menu not displayed in Droopler Active
6. 🐛 Footer menu - added links are not displayed (nav item is empty) Active

Done

1. 📌 [META] Droopler 3.x and Drupal 11 Active
2. 🐛 Updating Project Browser to version 2.0.0-alpha9 causes a critical error Active
3. 🐛 In Droopler the Gin cannot see the second tabs Active
4. 📌 New theme (colors) for Droopler 5.x Active
5. 🐛 Errors when changing the default home page from /welcome to another. Active
6. 🐛 Frontend editing sometimes fails to update the page Active
7. 🐛 Tiles gallery / Sidebar tiles - Colorbox does not display the image on the first attempt Active
8. 🐛 Tiles gallery - “feature image” option does not work Active
9. 🐛 The /search/node page is not working. Active
10. 📌 drupal/ala - has now D11 release - change code in composer.json Active

Next tasks

1. 🐛 Unidentified content in the reference content paragraph. Active
2. 🌱 Automated testing - Research Active
3. 🐛 Restore view of "Add Paragraph" Active
4. 🐛 Misaligned divider in banner section Active
5. 🐛 Improve spacing in paragraphs Active
6. 🐛 User account menu not displayed in Droopler Active
7. 🐛 Footer menu - added links are not displayed (nav item is empty) Active

Done

1. 📌 [META] Droopler 3.x and Drupal 11 Active
2. 🐛 Updating Project Browser to version 2.0.0-alpha9 causes a critical error Active
3. 🐛 In Droopler the Gin cannot see the second tabs Active
4. 📌 New theme (colors) for Droopler 5.x Active
5. 🐛 Errors when changing the default home page from /welcome to another. Active
6. 🐛 Frontend editing sometimes fails to update the page Active
7. 🐛 Tiles gallery / Sidebar tiles - Colorbox does not display the image on the first attempt Active
8. 🐛 Tiles gallery - “feature image” option does not work Active
9. 🐛 The /search/node page is not working. Active
10. 📌 drupal/ala - has now D11 release - change code in composer.json Active

I was able to downgrade from 3.4.4 to 8.3.3.0 and I can confirm this version is now marked as supported, thank you very much!

But I was wondering why not have version 3.4.4 supported instead of 8.3.3.0 which is still depended on the module Advanced CSS/JS Aggregation → ?

As you know, that module does not work well with Drupal 10.1+ and it is even recommended on the module page introduction to disable it until a new version is made available. The latest version dates back to January 2023 more than 2 years ago, development on it seems pretty much stalled for good as we can see on the issue queue especially on that one : https://www.drupal.org/project/advagg/issues/3409380 🐛 Alternative solution for advanced aggregation css / js Active

Also, having version 3.4.4 as the supported version for Drupal 10 would mean you do not have to maintain it as an intermediate version as a bonus and we would simply stay on it until ready to migrate to Drupal 11.

What do you think?

Thanks again for all your hard work, this is greatly appreciated!