Drush disable module drupal 9 install#
Drush disable module drupal 9 update#
Drush disable module drupal 9 download#

Root composer.json requires drupal/kint ^2.1 -> satisfiable by drupal/kint. drupal/kint 2.x-dev is an alias of drupal/kint dev-2.x and thus requires it to be installed too.

Drush disable module drupal 9 update#

Make sure you list it as an argument for the update command. drupal/kint require drupal/core ~8.0 -> found drupal/core but the package is fixed to 9.2.2 (lock file version) by a partial update and that version does not match. Your requirements could not be resolved to an installable set of packages. Loading composer repositories with package information

Drush disable module drupal 9 download#

Which means it should be possible to download it with just firing up the composer require drupal/kint command, right? However here is the log: This module is oficially part of Devel 8.x module. Now, the official page of Kint module at does not mention Drupal 9 yet, however thanks to core's compatibility layer we can use Drupal 8 modules on Drupal 9 websites, and since the same page states:

Drush disable module drupal 9 install#

So you install and enable it with Composer and Drush as any other Drupal 9 module: There is no problem with installing the Devel module as it already has versions released specifically for Drupal 9. It is easy to use, powerful and customizable and makes an essential addition to your development toolbox. Kint - a powerful and modern PHP debugging tool designed to present your debugging data in very convenient way replacing var_dump() and debug_backtrace(). Devel also features Drush integration and provides several custom Drush commands. The Devel module includes the Webprofiler, Devel generate and Kint modules. Develĭevel is a popular module containing a variety of developer and debugging tools that make it breeze to perform common development tasks. Now, first let's get to definitions of both development modules. And because most of tutorials found online on the subject turned out to be buggy, outdated and/or obsolete, for posterity reasons I decided to log the installation steps that worked for me.Ĭomposer require drupal/devel kint-php/kint NOTE: With a more complex install profile I expect to encounter more difficulty.I was recently setting up my local development environment for a new Drupal 9 project and despite abundance of documentation, couldn't get the Devel and Kint properly working at once. Test by removing the profiles/pushtape directory, clearing caches, and browsing around your site. That’s it - your site is now officially a vanilla Drupal install. The second tells Drupal that the “standard” install profile is active, and should be checked for updates. The first command removes the entry for the profile from Drupal’s system table - it removes any knowledge Drupal has that there was an install profile there. Technically these should both be covered by the registry_rebuild operation, but we’re doing it by hand because it seems to be missed in some operations. The easiest way to do this is from the SQL command line, which you can access via drush: drush sqlq 'DELETE FROM `system` WHERE filename LIKE 'profiles/profilename/profilename.profile'ĭrush sqlq 'UPDATE `system` SET status=1 WHERE filename LIKE 'profiles/standard/standard.profile'' We’re going to move them to a more normal location.Īs commenter notes, you may need some followup cleanup to really get all traces out. In the case of pushtape, we have libraries, modules, and a theme stored in there. The first step is going to be moving everything out of there. Install profiles have all their files stored in the site root’s profiles/ directory. Later I’ll return to this subject with the much more in-depth example of moving a community site away from Drupal Commons. Today I’ll use a relatively simple example of a musician site which is moving away from the Pushtape distribution.

Very often your site will diverge from the install profile as it takes on a life of its own, and it will be useful to convert it to “vanilla” Drupal. The assumption is that when you use an install profile, you want to rely on the profile’s maintainer for all your updates. What you did after the site was installed was your own business! But in Drupal 7 profiles are much more integrated with core. In Drupal 6, an Install Profile was just a blueprint for setting up a site really quickly. Install profiles are a great way to throw together a functional Drupal site really quickly.