Generally we want to use tarball releases from drupal.org since they include version tags in the module.info files that isn't in the repository. However, there are a few modules (such as Lawrence University's MM Tweaks) that don't go through the Drupal.org release process and are only available as a git repository. One option is to download a .zip of their module and add it like others. Alternatively, we can use git subtree to merge their repository (and all of its commits) into our repository under a sub-directory.
Let's say that you run a deployment to production but find that it caused more problems than it fixed. To resolve this issue we want to reset the production drupal directory back to its last operational point. You can do this all from the command line, but using gitk to identify your rollback point makes it much easier to see where you want to go.
Mastering Drupal 8 download.zip
i ve got errors indeed when want to enable a model but it installs normally: for drupal8 and the same for drupal seven Command pm-enable needs a higher bootstrap level to run - you will [error]need to invoke drush from a more functional Drupal environment to runthis command.The drush command 'en page_manager' could not be executed. [error]Drush was not able to start (bootstrap) the Drupal database. [error]Hint: This may occur when Drush is trying to: * bootstrap a site that has not been installed or does not have aconfigured database. In this case you can select another site with aworking database setup by specifying the URI to use with the --uriparameter on the command line. See `drush topic docs-aliases` fordetails. * connect the database through a socket. The socket file may bewrong or the php-cli may have no access to it in a jailed shell. See for details. 2ff7e9595c
Comentários