We use the ​Drupal Content Management System (CMS) for ​https://www.clarin.eu. ​A general, brief overview of Drupal.

Development follows a three-stage workflow:

1. development: tst.clarin.eu?
2. staging/acceptance: staging-www.clarin.eu?
3. production: www.clarin.eu?

Drupal should be managed from the command line with ​Drush. ​Commands for drush.

1. Historical situation

1.1. Drush availability

Drush is installed in Bas van der Veen and Jurriaan Roelof's home directories instead of in a system-wide $PATH directory. Users from the Unix group clarinadmin can access it. At this moment Bas van der Veen can perform Drush commands (in directory /hum/web/www.clarin.eu/htdocs/sites/clarin.eu or /hum/web/tst.clarin.eu/htdocs) /home/bvdveen/drush/drush status

The current version is outdated (5.8) and should be updated after planned OS upgrade (Feb 2016). Recent drush subcommands may not work otherwise.

In the following, let "${Drupal_root_dir_path}" be the root directory path of the Drupal installation.

1.2. Backups

ICT & Media system administrators are responsible for a regular backup through a filesystem(?) snapshot.

1.2.1. Manually, through web interface

​https://www.clarin.eu/admin/config/system/backup_migrate

1.2.2. Manually, from command line

With ​`archive-dump`

drush archive-dump # --no-core

​or:

drush bam

1.2.3. Manually, from command line (error prone version)

sudo tar -cvJ -C '/hum/web/www.clarin.eu/htdocs' -f ‘bckup_clarin_28oct15’ .

1.3. Which updates are available?

drush -r "${Drupal_root_dir_path}" -s core-status Drupal

Check if a module is listed under ../sites/all/patches. Patches are often integrated in higher non-patch versions of modules. See: ​https://www.drupal.org/patch (manually apply patch: ​https://www.drupal.org/node/534548).

---

# Or: '/hum/web/tst.clarin.eu/htdocs/'
cd '/hum/web/www.clarin.eu/htdocs/sites/clarin.eu/'
drush status
# List patches
drush ups --security-only 
# Apply patches
drush upc --security-only 

1.4. Common error messages

1.4.1. Wrong directory

Command pm-refresh needs a higher bootstrap level to run - you will need to invoke drush from a more         [error]
functional Drupal environment to run this command.

1.4.2. ups failed

The drush command 'ups' could not be found.  Run `drush cache-clear drush` to clear the commandfile cache if [error]
you have installed new extensions.

You did not use Drush 5 or higher. Instead, you could issue:

drush up --security-only

1.4.3. Forbidden to download drupal core

It's forbidden to download drupal core into an existing core. 

drush rf

# In case database migration is needed:
drush updb                              

# Should not show available updates or errors:
drush status                            

• Check website, and disable maintenance mode.
• Possibly, Drupal Features must be reset:

  drush features-list
  # Reset Drupal Features:
  drush fr -y openscience_demo_content openscience_events --force 
  

• In case the previous has failed, indicated by the status being overridden, consult ​https://www.drupal.org/node/986932. A quick fix is to remove and reinstall all Feature modules, but for custom Features (openscience, clarin_eric_config) that will fail.

1.4.4. Failed Drupal upgade …

​Restore from backup archive.