Ajouter un commentaire

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.

Plain text

  • Aucune balise HTML autorisée.
  • Les adresses de pages web et de courriels sont transformées en liens automatiquement.
  • Les lignes et les paragraphes vont à la ligne automatiquement.

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.
  • Pour publier des morceaux de code, entourez-les avec les balises <code>...</code>. Pour du PHP, utilisez. <?php ... ?>, ce qui va colorier le code en fonction de sa syntaxe.
  • Les adresses de pages web et de courriels sont transformées en liens automatiquement.
  • Tags HTML autorisés : <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Les lignes et les paragraphes vont à la ligne automatiquement.
By submitting this form, you accept the Mollom privacy policy.