How to install drupal 11.2.0 without composer?

Created on 21 June 2025, about 1 month ago

Since I can't use composer, is it possible to install drupal 11.2.0 without composer?
The zip file contains only Vendor and manual update is not possible.

thanks and regards

๐Ÿ’ฌ Support request
Status

Active

Version

11.2 ๐Ÿ”ฅ

Component

composer

Created by

๐Ÿ‡ฎ๐Ÿ‡นItaly giordy

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @giordy
  • Why canโ€™t you use Composer?

    Not using Composer really isnโ€™t supported.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly giordy

    I can't use composer because it's not included in the hosting plan, which I can't change because I'm not the owner of the site.

    Up until version 11.1.8 I've always managed to install it manually.

    Is there a full version to download like the previous ones?

    Thanks and regards

  • What is the method you have been using to upgrade Drupal manually on that hosting platform? Please be specific.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly giordy

    Semplicemente scarico il file zip completo e sostituisco i vecchi files con i nuovi. Sono anni che funziona senza problemi.

    lo zip drupal 11.1.8 รจ di 32.12 MB, mentre quello di drual 11.2.0 รจ di 4,39 MB

    Ho bisogno della versione completa di drupal 11.2.0 per fare la stessa operazione.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States xjm

    Drupal 10 and above no longer support installing or updating with the zip files, unfortunately. Composer is a requirement.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States xjm

    Although, that does sound like a bug with the file archive. Interesting. We should stop making them entirely if they're that broken.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States xjm
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States xjm

    For what it's worth, @giordy, you should be aware that even if we are able to fix these zip archives, they will stop working sometime in the near future, possibly within a year or so. Officially, they have not been a supported mechanism to update a Drupal site since Drupal 10 was released in 2022, and I would expect that we will stop creating them entirely within the next year or so. Therefore, I would make plans to migrate this site off its current hosting however you can as soon as possible.

  • @giordy As an alternative it is possible to build a set of files to deploy, using Composer on your laptop or some other computer. This will require setup on your end and itโ€™s a bit beyond the support we could offer hereโ€”in particular because it is not supported, but you could ask in Slack or elsewhere.

  • ๐Ÿ‡ธ๐Ÿ‡ฐSlovakia poker10

    If you download and extract it, the vendor directory contains mostly empty folders, so this looks like a bug.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

    This is likely a drupalorg or infrastructure issue for packaging. Iโ€™ll leave the issue here for findability, and move once closer to a fix.

    I think we do want to keep the tarball packaging in some form, it is somewhat of an end-to-end test of the subtree splits and project templates working correctly, and is one of the faster packaging steps.

    As far as I can tell, the subtree splits and templates look good for now.

    Tarball packaging would switch to recommended-project to support ๐Ÿ“Œ Remove drupal/legacy-project as a starting point for Drupal 10 Needs work , and removing / deprecating them will hopefully be more coordinated than them not being packaged correctly.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

    Looks like this was simply running on a too-old version of PHP. I am updating that, and adding exception handling if composer create-project fails.

    • drumm โ†’ committed 96fa0f04 on 7.x-3.x
      Issue #3531506: Use newer PHP for core packaging with composer, throw...
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

    Iโ€™ve deployed that fix and repackaged all 11.2.* releases. I believe that the downloads should be good now. And the additional error handling should show this type of problem earlier next time.

    Please follow ๐Ÿ“Œ Remove drupal/legacy-project as a starting point for Drupal 10 Needs work and related issues for future changes to supported file layouts (recommended-project vs legacy-project) and packaging. The downloadable packages are generated with Composer, so you can use them as a starting point and get modules and other dependencies with Composer, but it is best to use Composer from the start, so you are familiar with it.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly giordy

    Thanks for fixing the zip file.

    Unfortunately I do not agree with the choice that was made starting from Drupal 8.
    Once there was Drupal 7, with hundreds and hundreds of modules. It was the favorite CMS of Italian schools. Only a few used Joomla or WordPress. Courses were held and beautiful sites were built. I too, for my school, made a site with everything that could be needed.
    The forums were full of users who helped you develop these sites.
    Then Drupal 8 arrived with the use of Composer. It is unthinkable that volunteer teachers or, even worse, secretarial staff, with everything they have to do, have the will and the ability to tinker with Composer. The forums have emptied and schools have chosen other cms.
    In addition to schools there are freelancers, shops, artisans, parishes. How many use Drupal? Most of it is done with WordPress, but many use pre-packaged sites that can be found online. In addition to being easy to customize, they are also nice.
    Now there is no one left in the Italian forums.
    Drupal has become a cms only for professionals and I am not one; as long as I can manage the site without Composer, I will continue, and then ... I will have to look elsewhere.
    In my opinion, things have become unnecessarily complicated.
    As we are thinking about automatic updates of Drupal, we could have left the direct installation of the modules. For the dependencies, it was enough to implement Ludwig for all the modules and above all to ensure that the versions of the modules followed those of the core.

    Sorry for the outburst

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024