🇵🇱Poland @grzegorz.bartman

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.

Radix 6.x is needed to upgrade core to 11.x: https://www.drupal.org/project/droopler/issues/3501415 📌 Upgrade Radix from 5.x to 6.x Active

grzegorz.bartman → created an issue.

Fixed in https://www.drupal.org/project/drupalorg/issues/3500891 💬 Project statistics not visible in the "Project information" section, but the statistics page itself works Active - it was changed in Drupalorg code.

Thank you :)

I tested the installation and it works fine. I don't have any code comments. You can merge this code to the main branch.

grzegorz.bartman → created an issue.

Thank you for your interest in Droopler 5! It’s great to hear that you’re excited about the new version :)

Currently, we’ve decided to focus on improving Droopler with exciting features like new theme colors and additional functionality. To ensure we can dedicate our resources to these improvements, we’ve opted to support only one installation method: DDEV.

If you’d like to try installing Droopler 5 without DDEV, you can follow the steps that are in the launch-droopler-cms.sh file in the repository.

In theory, you can replicate the steps manually in your terminal. Here’s an untested guide:

1. Clone the repository:
git clone [repository-url] [directory-name]

2. Navigate into the directory:
cd [directory-name]

3. Install dependencies with Composer:
composer install

4. Copy the starter theme into the appropriate directory:
cp -r starter-theme/ web/themes/custom/

5.Move the necessary Droopler profile files:
mv droopler.info.yml web/profiles/droopler/droopler.info.yml
mv droopler.profile web/profiles/droopler/droopler.profile

6. Open your browser and proceed with the setup.

If you’d like to customize the theme, there’s a theme command in the ddev_commands directory to compile styles. This can be helpful if you want to tweak colors or styles.

Keep in mind, though, that this method isn’t officially supported, and we haven’t tested it extensively. If you give it a try, feel free to share your experience with the community!

Works fine after changing branch:

git clone git@git.drupal.org:issue/droopler-3500842.git droopler1
cd droopler1
git checkout origin/3500842-default-content-option
./launch-droopler-cms.sh
ddev launch

You can merge it to the main branch and release a new version with this option.

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

I tested it using these steps:

git clone git@git.drupal.org:issue/droopler-3500842.git droopler1
cd droopler1
./launch-droopler-cms.sh
ddev launch

In the browser, I get a standard installation process without any option to check or uncheck demo content installation.
Are my testing steps correct?

grzegorz.bartman → created an issue.

grzegorz.bartman → created an issue.

Version 4.x will be no longer developed. I'm closing this issue.

Version 4.x will be no longer developed. I'm closing this issue.

Version 4.x will be no longer developed. I'm closing this issue.

Version 4.x will be no longer developed. I'm closing this issue.

Version 4.x will be no longer developed. I'm closing this issue.

Version 4.x will be no longer developed. I'm closing this issue.

We will review this problem today. The tag is not visible on Packagist.

When I was reading the doc list of contents here: https://git.drupalcode.org/project/distributions_recipes/-/tree/1.0.x?re..., the title in point 4 was misleading for me. The “Recipe types” page mainly refers to recipe names, but I thought it would be about the recipe.yml file and the “Type” parameter.

esmoves → credited grzegorz.bartman → .

Hi,

We just updated the readme file. Thanks for reporting this issue :)

Correct command to create project based on 4.x alpha version:

composer create-project droptica/droopler-project:^4.0-alpha <path>

I did not even know "Site" type recipes exist

"Additionally, the type 'Site' means that the Drupal recipe will be listed in the installer. " - this information is in example Drupal recipe file https://git.drupalcode.org/project/distributions_recipes/-/blob/1.0.x/do...

I agree, the word "conflict" should be changed to war

Good meeting! Thanks :)

Thanks for the meeting! :)

I will share drupalcamp.pl codebase as soon I will find out where it is :)