I think it's worth training AI to globally update the compatibility of all modules that are on git.drupalcide.org . This will save thousands of developer hours. I think it's possible now.
Since the modules can now be installed from the browser, I'm afraid this problem will be bigger. Many applications will have many more modules installed than the basic recipes. This means that when upgrading to Drupal 12, these sites will not be able to update until the installed modules are updated. Ideally, all modules that are installed from the browser should be constantly updated, at least in the same amount as wordpress. When installing the wordpress plugin, I'm not worried that it will work in the future, as everything is updated on time. This will have to be resolved in the near future.
Yes, you're right. There is no guarantee that a third-party module will not be broken with each update. Thanks for the link
Yes, you're right. There is no guarantee that a third-party module will not be broken with each update. Thanks for the link
Yes, you're right. There is no guarantee that a third-party module will not be broken with each update. Thanks for the link
Drupal cms uses a lot of third-party modules, which is great. That's why I'm referring to the drupal cms, not the drupal core, since an important component of the drupal cms is the trouble-free operation of the core and third-party modules. Therefore, it's worth thinking about how to keep up-to-date third-party modules. You should not leave users alone with abandoned or rarely updated modules. Some modules have not been updated for years, but are used on thousands of sites. Users do not upgrade to new versions of drupal due to the fact that developers have abandoned or for some reason do not update modules. A strategy is needed to solve this problem. Because this is a global issue and no less important than the drupal core updates.
volanar → created an issue.
I tried to install drupal through the web installer several times, but the installation ended with errors. There have always been different mistakes, so I'll wait for it to be fixed.
And the biggest problem of the installation is the inflated database versions. The developers are guided by the date of database support, but do not take into account that each hosting has different versions of databases that cannot be updated with drupal. Therefore, drupal has taken a big step back by allowing only new versions of databases to be installed. But for example, postgres 15 support will end in 3 years, and drupal with postgres 15 cannot be installed with drupal version 11. Why not do it in two years?
This is good when a fresh installation is necessary, but in 90 percent of cases we update drupal with an existing database. And updating the database is not so easy and not always possible, especially when it is used by other scripts. This must be taken into account
volanar → created an issue.
root@***:/var/www/***usr/data/www/***.com# composer create-project drupal/cms:1.0.x-dev -s dev
Creating a "drupal/cms:1.0.x-dev" project at "./cms"
Installing drupal/cms (1.0.x-dev d85a2561b95694e43ed5c29d25d8b238d3cbe318)
- Installing drupal/cms (1.0.x-dev d85a256): Extracting archive
Created project in /var/www/portal_neovk_usr/data/www/portal.neovk.com/cms
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/drupal_cms_ai 1.0.x-dev -> satisfiable by drupal/drupal_cms_ai[1.0.x-dev].
- drupal/drupal_cms_ai 1.0.x-dev requires drupal/drupal_cms_privacy_basic 1.0.x-dev -> found drupal/drupal_cms_privacy_basic[1.0.x-dev] but it does not match your minimum-stability.
Problem 2
- Root composer.json requires drupal/drupal_cms_analytics 1.0.x-dev -> satisfiable by drupal/drupal_cms_analytics[1.0.x-dev].
- drupal/drupal_cms_analytics 1.0.x-dev requires drupal/drupal_cms_google_analytics 1.0.x-dev -> found drupal/drupal_cms_google_analytics[1.0.x-dev] but it does not match your minimum-stability.
Problem 3
- Root composer.json requires drupal/drupal_cms_events 1.0.x-dev -> satisfiable by drupal/drupal_cms_events[1.0.x-dev].
- drupal/drupal_cms_events 1.0.x-dev requires drupal/drupal_cms_privacy_basic 1.0.x-dev -> found drupal/drupal_cms_privacy_basic[1.0.x-dev] but it does not match your minimum-stability.
Problem 4
- Root composer.json requires drupal/drupal_cms_forms 1.0.x-dev -> satisfiable by drupal/drupal_cms_forms[1.0.x-dev].
- drupal/drupal_cms_forms 1.0.x-dev requires drupal/drupal_cms_anti_spam 1.0.x-dev -> found drupal/drupal_cms_anti_spam[1.0.x-dev] but it does not match your minimum-stability.
Problem 5
- Root composer.json requires drupal/drupal_cms_page 1.0.x-dev -> satisfiable by drupal/drupal_cms_page[1.0.x-dev].
- drupal/drupal_cms_page 1.0.x-dev requires drupal/drupal_cms_content_type_base 1.0.x-dev -> found drupal/drupal_cms_content_type_base[1.0.x-dev] but it does not match your minimum-stability.
Problem 6
- Root composer.json requires drupal/drupal_cms_person 1.0.x-dev -> satisfiable by drupal/drupal_cms_person[1.0.x-dev].
- drupal/drupal_cms_person 1.0.x-dev requires drupal/drupal_cms_content_type_base 1.0.x-dev -> found drupal/drupal_cms_content_type_base[1.0.x-dev] but it does not match your minimum-stability.
Problem 7
- Root composer.json requires drupal/drupal_cms_starter 1.0.x-dev -> satisfiable by drupal/drupal_cms_starter[1.0.x-dev].
- drupal/drupal_cms_starter 1.0.x-dev requires drupal/drupal_cms_admin_ui 1.0.x-dev -> found drupal/drupal_cms_admin_ui[1.0.x-dev] but it does not match your minimum-stability.
Problem 8
- Root composer.json requires drupal/drupal_cms_project 1.0.x-dev -> satisfiable by drupal/drupal_cms_project[1.0.x-dev].
- drupal/drupal_cms_page 1.0.x-dev requires drupal/drupal_cms_content_type_base 1.0.x-dev -> found drupal/drupal_cms_content_type_base[1.0.x-dev] but it does not match your minimum-stability.
- drupal/drupal_cms_project 1.0.x-dev requires drupal/drupal_cms_page 1.0.x-dev -> satisfiable by drupal/drupal_cms_page[1.0.x-dev].
root@***:/var/www/***_usr/data/www/***.com#
Drupal CMS has been announced, but it is impossible to install it. Not through Composer, not manually. Probably, they forgot about Drupal because of the celebration)
volanar → created an issue. See original summary → .
volanar → created an issue.