Drupal is a registered trademark of Dries Buytaert
drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)! drupal 11.3.6 Update released for Drupal core (11.3.6)! drupal 10.6.6 Update released for Drupal core (10.6.6)! cms 2.1.0 Update released for Drupal core (2.1.0)! bootstrap 8.x-3.40 Minor update available for theme bootstrap (8.x-3.40). menu_link_attributes 8.x-1.7 Minor update available for module menu_link_attributes (8.x-1.7). eca 3.1.1 Minor update available for module eca (3.1.1). layout_paragraphs 2.1.3 Minor update available for module layout_paragraphs (2.1.3). ai 1.3.3 Minor update available for module ai (1.3.3). ai 1.2.14 Minor update available for module ai (1.2.14). node_revision_delete 2.0.3 Minor update available for module node_revision_delete (2.0.3). moderated_content_bulk_publish 2.0.52 Minor update available for module moderated_content_bulk_publish (2.0.52). klaro 3.0.10 Minor update available for module klaro (3.0.10). klaro 3.0.9 Minor update available for module klaro (3.0.9). layout_paragraphs 2.1.2 Minor update available for module layout_paragraphs (2.1.2). geofield_map 11.1.8 Minor update available for module geofield_map (11.1.8).

batch_content_sync

21 sites No security coverage
View on drupal.org

🌀 Batch Content Sync

Push and sync content across Drupal environments with ease.

Batch Content Sync helps editors send content to QA, Stage, or Prod using a streamlined interface and REST endpoints.

🚀 Features

Batch Content Sync provides a lightweight, editor-friendly solution for synchronizing content between Drupal environments such as QA, Stage, and Production.

Key Features:

  • Push content (nodes) to QA, Stage, or Production from the content overview page.
  • Custom REST endpoints for receiving structured content payloads.
  • Automatically includes referenced media, taxonomy terms, and paragraph items.
  • Built-in access token authentication—no need for external contrib modules.
  • Clean JSON logging of push attempts for troubleshooting or audit history.
  • Minimal dependencies—ideal for lean, CI/CD-friendly deployments.

Use Cases:

  • Editorial teams staging content before production release.
  • Development workflows requiring content parity across environments.
  • Automating deployments of updated or newly published content.
  • Reducing manual duplication effort and copy-paste errors.

⚙️ Post-Installation

After installing the module, visit the configuration page at:

/admin/config/content/batch-content-sync

There you can define the target environment URLs (e.g., QA, Stage, Prod) and set the access token for secured communication.

To use the module:

  1. Navigate to Content overview at /admin/content.
  2. Select one or more content items (nodes).
  3. From the Action dropdown, choose:
    • Push to QA
    • Push to Stage
    • Push to Prod

Your content will be pushed via custom REST calls to the configured target.

📦 Additional Requirements

No contrib dependencies required. Works with Drupal Core only.

Make sure:

  • The target site also has Batch Content Sync installed.
  • REST endpoints are accessible.
  • Access tokens match between environments.

đź”§ Recommended Modules / Libraries

Optional but useful enhancements:

  • Diff – for comparing content before and after sync.
  • Paragraphs – supported out-of-the-box.
  • Media – also supported for embedded assets.

đź’¸ Supporting this Module

If this module saves you time or budget, you can support development here:

  • 🧉 Buy me a coffee
  • 🤝 Sponsor feature requests via GitHub or issue queue

📚 Community Documentation

  • Basic docs available in the module’s README.md.
  • More coming soon — including video walkthroughs and tutorials.
  • Want to contribute? PRs and edits are welcome!

Activity

Total releases
5
First release
Jul 2025
Latest release
7 months ago
Release cadence
10 days
Stability
80% stable

Release Timeline

Releases

Version Type Release date
2.0.2 Stable Sep 9, 2025
2.0.1 Stable Aug 30, 2025
2.0.0 Stable Aug 8, 2025
1.0.0 Stable Jul 31, 2025
1.0.x-dev Dev Jul 31, 2025