Content Staging for Drupal, BADcamp presentation

Ever since Drupal started to hit the big time, anyone talking about workflows and process at a Drupal con or camp has probably been asked this question:

'How can I migrate content from one Drupal site to another, so I can review changes before they go live?'

I call this the Drupal content staging problem, and I've never had a good answer for it. Until now. In this BADcamp 2012 presentation, I described how to use the Services Client module and UUIDs to manage bi-directional editing of content across multiple sites, allowing a variety of workflows, including content staging.

The demo site source code and databases, instructions for using them, and presentation slides are available at https://github.com/bjaspan/drupal-content-staging.

Comments

Posted on by interested (not verified).

Hi,
Does the system handle block,views etc ? and if a field is missing on the target system publish it to the target system ?

Garry

Posted on by answer (not verified).

Could you answer the question above please ?

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.