Updating drupal modules
This module has stable versions for Drupal 6 & 7 but there’s not one for Drupal 8.
However Lucian Hangea (@lhangea) have been porting this module as his project for Google Summer Of Code (GSo C).
For those of you who also manage your sites in you know that simply copying the latest version of Drupal over top of the old version doesn’t cut it.
Even some scripted methods can be cumbersome if the changes are complex.
Next, add a subfolder to “vendors” either called “acquia” or “drupal” depending which version you are using.
Now, that the repo structure is correct we need to import the historic version of Drupal (that is the version you’re currently running your site on and is out of date).
Note that for each release there are two options, “New Install” and “Upgrade”.
If you don’t have a branches and tags folder, its recommended but you can proceed with this tutorial without.
If you don’t have a “vendors” folder, go ahead and create it now.
The “latest version” which is the most up to date version of Drupal and the “historic version” of Drupal which is what your site is currently running.
(As a point of illustration, if the latest version and historic version were the same the “changeset” that would result would be empty, but it would work theoretically.) Acquia Drupal: For those of you following along with Acquia Drupal.
Search for updating drupal modules:
I recommend using the “New Install”, because this will keep track of changes to the settings and htaccess file which we may want to be aware of.