🇵🇱Poland @grzegorz.bartman

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

Next tasks

1. 📌 Documents - change filesystem to private Active
2. 📌 View /documents - add information about references to each document Active

Done

1. 📌 Rename profile from d_intranet to openintranet Active

grzegorz.bartman → created an issue.

Next tasks

1. 📌 View /documents - add information about references to each document Active

Done

1. 📌 Rename profile from d_intranet to openintranet Active

grzegorz.bartman → created an issue.

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

grzegorz.bartman → created an issue.

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

grzegorz.bartman → created an issue.

Thanks for reporting this.

Did I do something wrong during installation, or is this normal behaviour?

This is "normal" behavior :)
We know this problem, but with this warning, Droopler installs properly, so it is a low priority on our tasks list.

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

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

Thanks for reporting this. I added this on our next tasks list 🌱 [META] Priorities & next tasks - Droopler 3.x and 5.x 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

Thank you for your response! I understand the situation. If anything changes in the future, please let me know – we'd be happy to help or take over the project.

By the way, our own intranet is already available as open source, so the community can freely use it.

https://git.drupalcode.org/sandbox/grzegorz.bartman-3513334

Best regards, Grzegorz

grzegorz.bartman → created an issue.

Done.
Droopler 3.5.9 is compatible with Drupal 11.

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

grzegorz.bartman → created an issue.

We'd like to use this namespace https://www.drupal.org/project/intranet →

Currently, the project is in a private repository.
Here you can see quick demo https://www.youtube.com/watch?v=2Y_NHEpFXkU

Here we will publish it on Wednesday/Thursday for testing https://www.drupal.org/sandbox/grzegorzbartman/3513334 →

We want to publish it as a distribution to have a usage statistics page (like we have with Droopler https://www.drupal.org/project/usage/droopler → ), so it is important to know what namespace we will have :) As I know namespace on drupal.org should be the same as the installation profile name in the code in the git repository.

Plan for D11 and Droopler 3.x
- we will release 3.4 version - that will uninstall Advagg module
- then we will release 3.5 version - this will be compatible with Drupal 11.x

Thanks for reporting. I added it to our priority list 🌱 [META] Priorities & next tasks - Droopler 3.x and 5.x Active

Thanks for your patience and sorry for the late reply!

I've just created a new task to track our current priorities here: 🌱 [META] Priorities & next tasks - Droopler 3.x and 5.x Active .

To quickly summarize our recommendations:

1. For new websites: Definitely use Droopler 5.x, as it's the most up-to-date and future-proof version.
2. For existing websites on 3.x: We'll keep supporting these sites, but our focus will only be on bug fixes and security updates—no major improvements or features.
3. For existing websites on 4.x-alpha: We recommend removing/uninstalling the Droopler profile and continuing as a standard Drupal site to simplify future maintenance.

We really appreciate your feedback and involvement :)

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

Comment from GitHub issue: Cannot reproduce the problem. I'm closing this issue.

Moving to 5.x but with low priority.

Moving to 5.x but with low priority.

Droopler 5.x now uses Bootstrap 5. I'm closing this issue.

We marked this task as a priority for Droopler 3.x

Update:

-Proposed "solution" after testing and internal discussion: remove the language select option from the installation process (in DrupaLCMS lang switcher is also removed)

It is a question related to your local environment. I suggest trying to ask in ChatGPT or a similar AI tool or ask on slack in the Droopler channel, perhaps someone will know the answer. I'm closing this issue.

Update:

- https://www.drupal.org/project/ala → module is still in D10 version only
-Next step: propose solutions on how to upgrade Droopler to Drupal 11

When is a new D11 compatible version planned?

grzegorz.bartman → created an issue.

Status: waiting for patch https://www.drupal.org/project/ala/issues/3442409 📌 Automated Drupal 11 compatibility fixes for ala Needs review

Reviews and tested by 2 developers in Droptica

Testing steps:

git clone git@git.drupal.org:issue/droopler-3501307.git
cd droopler-3501307
git checkout 3501307-d11
./launch-droopler-cms.sh

Output after this test:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/ala ^2.5 -> satisfiable by drupal/ala[2.5.0].
    - Root composer.json requires drupal/core-recommended ^11 -> satisfiable by drupal/core-recommended[11.0.0-alpha1, ..., 11.x-dev].
    - Root composer.json requires drupal/twig_tweak ^3.4 -> satisfiable by drupal/twig_tweak[3.4.0, 3.x-dev].
    - drupal/ala 2.5.0 requires drupal/core ^8 || ^9 || ^10 -> satisfiable by drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev].
    - drupal/core[8.0.0-beta13, ..., 8.0.0-beta15] require guzzlehttp/guzzle dev-master#1879fbe853b0c64d109e369c7aeff09849e62d1e -> found guzzlehttp/guzzle[dev-set-cookie-typing, dev-test, v1.0.3, v1.0.4, v2.0.0, ..., v2.8.8, v3.0.0, ..., v3.8.1, 4.0.0-rc.1, ..., 4.x-dev, 5.0.0, ..., 5.3.x-dev, 6.0.0, ..., 6.5.x-dev, 7.0.0-beta.1, ..., 7.9.x-dev, 8.0.x-dev] but it does not match the constraint.
    - drupal/core 8.0.0-beta6 requires doctrine/common dev-master#a45d110f71c323e29f41eb0696fa230e3fa1b1b5 -> found doctrine/common[dev-remove-int-cast, dev-3.4.x-merge-up-into-3.5.x_ERxP2qhI, dev-3.4.x-merge-up-into-3.5.x_Nw2dYaQO, 2.1.3, ..., 2.13.x-dev, 3.0.0, ..., 3.6.x-dev] but it does not match the constraint.
    - drupal/core[8.2.0-beta1, ..., 8.3.x-dev] require symfony-cmf/routing ~1.4 -> satisfiable by symfony-cmf/routing[1.4.0-RC1, ..., 1.4.x-dev].
    - drupal/core[8.4.0-alpha1, ..., 8.7.7] require symfony-cmf/routing ^1.4 -> satisfiable by symfony-cmf/routing[1.4.0-RC1, ..., 1.4.x-dev].
    - drupal/core[8.7.8, ..., 8.9.10] require symfony/psr-http-message-bridge ^1.1.2 -> satisfiable by symfony/psr-http-message-bridge[v1.1.2, 1.1.x-dev, v1.2.0, v1.3.0].
    - drupal/core[8.8.0-alpha1, ..., 8.8.x-dev] require zendframework/zend-feed ^2.12 -> satisfiable by laminas/laminas-feed[2.12.0, ..., 2.24.x-dev], zendframework/zend-feed[2.12.0, 2.12.x-dev, 2.13.x-dev].
    - drupal/core[8.9.11, ..., 8.9.x-dev] require php ^7.0.8 -> your php version (8.3.16) does not satisfy that requirement.
    - drupal/core[9.0.0-alpha1, ..., 9.0.0-alpha2] require symfony/psr-http-message-bridge ^1.2.0 -> satisfiable by symfony/psr-http-message-bridge[v1.2.0, v1.3.0].
    - drupal/core[9.0.10, ..., 9.0.x-dev] require php ^7.3 -> your php version (8.3.16) does not satisfy that requirement.
    - drupal/core-recommended 11.0.0-rc1 requires drupal/core 11.0.0-rc1 -> satisfiable by drupal/core[11.0.0-rc1].
    - drupal/core-recommended 11.0.0-alpha1 requires twig/twig ~v3.9.3 -> satisfiable by twig/twig[v3.9.3].
    - drupal/core-recommended 11.0.0-beta1 requires drupal/core 11.0.0-beta1 -> satisfiable by drupal/core[11.0.0-beta1].
    - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> satisfiable by drupal/core[11.0.0].
    - drupal/core-recommended 11.0.1 requires drupal/core 11.0.1 -> satisfiable by drupal/core[11.0.1].
    - drupal/core-recommended 11.0.10 requires drupal/core 11.0.10 -> satisfiable by drupal/core[11.0.10].
    - drupal/core-recommended 11.0.2 requires drupal/core 11.0.2 -> satisfiable by drupal/core[11.0.2].
    - drupal/core-recommended 11.0.3 requires drupal/core 11.0.3 -> satisfiable by drupal/core[11.0.3].
    - drupal/core-recommended 11.0.4 requires drupal/core 11.0.4 -> satisfiable by drupal/core[11.0.4].
    - drupal/core-recommended 11.0.5 requires drupal/core 11.0.5 -> satisfiable by drupal/core[11.0.5].
    - drupal/core-recommended 11.0.6 requires drupal/core 11.0.6 -> satisfiable by drupal/core[11.0.6].
    - drupal/core-recommended 11.0.7 requires drupal/core 11.0.7 -> satisfiable by drupal/core[11.0.7].
    - drupal/core-recommended 11.0.8 requires drupal/core 11.0.8 -> satisfiable by drupal/core[11.0.8].
    - drupal/core-recommended 11.0.9 requires drupal/core 11.0.9 -> satisfiable by drupal/core[11.0.9].
    - drupal/core-recommended 11.0.x-dev requires drupal/core 11.0.x-dev -> satisfiable by drupal/core[11.0.x-dev].
    - drupal/core-recommended 11.1.0-rc1 requires drupal/core 11.1.0-rc1 -> satisfiable by drupal/core[11.1.0-rc1].
    - drupal/core-recommended 11.1.0-beta1 requires drupal/core 11.1.0-beta1 -> satisfiable by drupal/core[11.1.0-beta1].
    - drupal/core-recommended 11.1.0 requires drupal/core 11.1.0 -> satisfiable by drupal/core[11.1.0].
    - drupal/core-recommended 11.1.1 requires drupal/core 11.1.1 -> satisfiable by drupal/core[11.1.1].
    - drupal/core-recommended 11.1.x-dev requires drupal/core 11.1.x-dev -> satisfiable by drupal/core[11.1.x-dev].
    - drupal/core-recommended 11.x-dev requires drupal/core 11.x-dev -> satisfiable by drupal/core[11.x-dev].
    - laminas/laminas-feed[2.12.0, ..., 2.12.x-dev] require php ^5.6 || ^7.0 -> your php version (8.3.16) does not satisfy that requirement.
    - zendframework/zend-feed[dev-master, dev-develop, 2.11.0, ..., 2.13.x-dev] require php ^5.6 || ^7.0 -> your php version (8.3.16) does not satisfy that requirement.
    - laminas/laminas-feed[2.13.0, ..., 2.14.x-dev] require php ^7.3 || ~8.0.0 -> your php version (8.3.16) does not satisfy that requirement.
    - symfony-cmf/routing[1.4.0-RC1, ..., 1.4.x-dev] require php ^5.3.9|^7.0 -> your php version (8.3.16) does not satisfy that requirement.
    - symfony/psr-http-message-bridge[v1.1.0, ..., 1.1.x-dev] require php ^5.3.3 || ^7.0 -> your php version (8.3.16) does not satisfy that requirement.
    - symfony/psr-http-message-bridge[v1.2.0, ..., v1.3.0] require php ^7.1 -> your php version (8.3.16) does not satisfy that requirement.
    - Conclusion: don't install drupal/core 11.1.x-dev (conflict analysis result)
    - Conclusion: don't install drupal/core 11.x-dev (conflict analysis result)
    - Conclusion: don't install twig/twig v3.9.3 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0-beta1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0-rc1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.2 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.3 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.4 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.5 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.6 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.7 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.8 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.9 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.10 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.0-beta1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.0-rc1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.0 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.1 (conflict analysis result)
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.0.0-beta12, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.1.2, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.1.8, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.7.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].

Composer [install] failed, composer command failed: exit status 2. stderr=

Todo:
- resolve conflict
- merge

After internal discussion we decided to change H3 in subtitle to SPAN tag

We will work on this in 5.x version.

Possible solutions:

• a) change H3 to
• b) add option to manually set Header type (H1, H2, H3, etc)

esmoves → credited grzegorz.bartman → .

grzegorz.bartman → created an issue.