🇬🇧United Kingdom @FlusteredLondon

The original branch was created under D10.x and the DrupalPod install failed to run (Composer dependencies).

This branch has the update to D11.x (command line '$ git rebase 11.x ' ).

Now possible to review properly.

Working at the moment to get this branch working for D11

Noob here: I tried to spin this up in DrupalPod with D11, but there are issues with Composer Dependencies. Can anyone assist?

--------------------

Problem 1
- Root composer.json requires drupal/core == 11.9999999.9999999.9999999-dev (exact version match), it is satisfiable by drupal/core[11.x-dev] from composer repo (https://repo.packagist.org) but drupal/core[dev-3220216-move-themespage-to, 10.2.x-dev] from path repo (repos/drupal/core) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Problem 2
- Root composer.json requires drupal/core-project-message == 11.9999999.9999999.9999999-dev (exact version match), it is satisfiable by drupal/core-project-message[11.x-dev] from composer repo (https://repo.packagist.org) but drupal/core-project-message[dev-3220216-move-themespage-to, 10.1.x-dev] from path repo (repos/drupal/composer/Plugin/ProjectMessage) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Problem 3
- Root composer.json requires drupal/core-recommended == 11.9999999.9999999.9999999-dev -> satisfiable by drupal/core-recommended[11.x-dev].
- drupal/core-recommended 11.x-dev requires drupal/core 9.3.x-dev -> satisfiable by drupal/core[9.3.x-dev] from composer repo (https://repo.packagist.org) but drupal/core[dev-3220216-move-themespage-to, 10.2.x-dev] from path repo (repos/drupal/core) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Problem 4
- Root composer.json requires drupal/core-dev == 11.9999999.9999999.9999999-dev -> satisfiable by drupal/core-dev[11.x-dev].
- drupal/core-dev 11.x-dev requires symfony/browser-kit ^4.4 -> found symfony/browser-kit[v4.4.0-BETA1, ..., 4.4.x-dev] but these were not loaded, likely because it conflicts with another require.

I tried to work on this, but the existing fork does not install correctly - looks like an issue with composer dependencies.

Should I ignore the fork and make another?

------------------------------

 Problem 1
    - Root composer.json requires drupal/core-recommended == 11.9999999.9999999.9999999-dev -> satisfiable by drupal/core-recommended[11.x-dev].
    - drupal/core-recommended 11.x-dev requires drupal/core 10.2.x-dev -> satisfiable by drupal/core[10.2.x-dev] from composer repo (https://repo.packagist.org) but drupal/core[dev-3380239-date-token-descriptions, 11.x-dev] from path repo (repos/drupal/core) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Failed to execute command composer update --lock: exit status 2
Failed to run exec_dir composer update --lock; error=exit status 1

I'm working on this at DrupalCon 2023

Based on the comments above from @marvil07, moving to RTC as not necessary.

@lauriii - are you happy with this?

Reviewing at Drupalcon 2023.

Checked:

• /admin/structure/menu/add
• /admin/structure/block-content/add

Both are updated.

I'm at Drupalcon Lille, and working on this today..