Drush commands for Configuration Management for Drupal 7

Command (shortcut in parentheses) Description Examples and Options
config-get-identifiers (cget) Return the list of identifiers for a given component.

Arguments:

The name of the component to get the identifiers.

Example:

drush cgi content_type
Returns the list of all available content types to export

Installing Drush On Any Linux Based Server Out There

NOTICE: Drush no longer supports installation via pear. As a result, much of this content is out of date. Please refer to the official documentation for installing Drush via composer.

Ok, so I am just conveying my experience in installing the quintessential tool that is drush. I work at Kalamuna and I provide support to a majority of our clients. I am constantly having to move sites around from server to server, platform to platform, etc.

Drush and Hooks

Hello,
i have installed the ldap module, which makes it possible to sync a user with active directory, when a user is created or updated.
When creating a user through the user administration, the sync is performed perfectly. But i'm trying to create a script, which can fetch all users from ldap and create them afterwards. But when created, the "sync" with ldap is not done. Are hooks not triggered, when using: drush script ?

drush permission denied command

I have install drush tool in my window8, it work well when the beginning
but after I run drush ld some_module not in the main directory of drupal project.
I just get a error:

C:\xampp\htdocs\drupal7\sites\all>drush ld view
require_once(C:\xampp\htdocs\drupal7\sites\all): failed to open [warning]

stream: Permission denied command.inc:1511
Drush command terminated abnormally due to an unrecoverable error. [error]

Why are some fields missing from an export from drush but not from the UI?

Situation

  • Have a views data export display
  • Output is fine when using Drupal UI
  • Output is missing Field UI fields when using Drush

Field Permissions Installed

  • Drush runs views data export as anonymous user causing view to not retrieve fields the user does not have access to because of field permissions.
  • Drush may be run as a different user with the user argument: drush --user=1 vde

Reference to EntityReference Field Migration

DESCRIPTION

This module converts references fields (from references module) to entity reference fields. A batch task will be issued (per field) to create a temporary table, store the reference values, delete the reference field, create a new
entity reference field, and copy over the values from the temporary table.

USAGE

There are 2 possible ways to convert fields:

USER INTERFACE

Go to admin/content/migrate-references, select the fields you wish to convert, and click confirm.

DRUSH

Type 'drush entityreference-migrate-references' (or 'drush emr') to convert all fields. You may provide a field machine name as an argument to convert on a field-by-field basis.

PRE-CONVERSION TASK LIST

Before starting any conversion, there are a few recommended tasks.

FIELDS

  1. Create a where-used list of fields, widgets and formatters, using:

VIEWS

  1. Create a where-used list of fields, filter criteria, sort criteria, contextual filters, using:
    • views: /admin/reports/fields/views-fields

Pages

Subscribe with RSS Subscribe to RSS - drush