default_content_deploy 2.0.0

Git tag 2.0.0
Bug fixes
New features

This module does not depend on the Default Content module (default_content)!

If you want to export files you should install the optional requirement Better Normalizers (better_normalizers).

If you want toe export Layout Builder settings per entity or translations you'll currently run into two core issues you should patch:

default_content_deploy 2.0.x-dev

Git branch 2.0.x
Bug fixes
New features

dev snapshot

default_content_deploy 8.x-1.0-beta3

Git tag 8.x-1.0-beta3
Bug fixes
  • Refactoring replace host in Importer.php
  • #3166563: by Murz, miroslav-lee: Add support for Default Content 2.x branch
  • #3127786: by rakshith.thotada, simoneb, miroslav-lee: Type User does not correspond to an entity on this site

default_content_deploy 8.x-1.0-beta2

Git tag 8.x-1.0-beta2
Bug fixes
  • Fixed a lot of other bugs.
  • #3122224: Fatal error when try to export vocabulary with terms using GUI

default_content_deploy 8.x-1.0-beta1

Git tag 8.x-1.0-beta1
Bug fixes
New features
  • Refactoring a lot of code. Now the code is more standardized, formatted, readable, supported, and match to the OOP.
  • Add GUI for importing and settings of this module
  • #3070222: Export to tar VIA GUI
  • #3068240: Allow importing of content with conflicting IDs

default_content_deploy 8.x-1.0-alpha7

Git tag 8.x-1.0-alpha7
Bug fixes

Fixed default_content dependency

default_content_deploy 8.x-1.0-alpha6

Git tag 8.x-1.0-alpha6
New features
  • Skip access check when exporting content
  • Use $settings instead of $config for content directory (with deprecated warning)
  • Remove Drush dependency from export service
  • Full export for user entities (roles, staus, etc.)
  • Full import for user entities - update operation is enabled (warning: recreating user entity during drush dcdi --force-update resets the password)

See README for more information.

default_content_deploy 8.x-1.0-alpha5

Git tag 8.x-1.0-alpha5
Bug fixes

Fix logic for exporting entities.
All entities of given type are exported only if no bundle and no specific IDs are defined in dcde or dcder drush command.

Command drush dcde node --bundle=page
will export only nodes of content type "page". If there is no content of bundle "page", no content will be exported.

Command drush dcde node
will export all nodes of all content types.

default_content_deploy 8.x-1.0-alpha4

Git tag 8.x-1.0-alpha4
New features

Important changes

drush dcdes
Command updated. Exports a whole site content.
Option --add_entity_type is removed, because command detects all content entity types and exports all its content by default.
You can still exclude any content entity type from the export.
Config directory will be emptied and all content of all entities will be exported.

dcd-entity-list
New command. Displays all current content entity types. Useful for choosing which to skip during the export.

default_content_deploy 8.x-1.0-alpha3

Git tag 8.x-1.0-alpha3
Bug fixes

Use $config['content_directory'] for definition of export/import content directory.
Using of $config_directories['content_directory'] is not recommended, because it causes unnecessary questions during drush cim or cex commands. But it was (by mistake) implemented in 8.x-1.0-alpha1 and 8.x-1.0-alpha2, so there is implemented a backward compatibility (both ways can be used).

Most coding standard issues have been fixed.

default_content_deploy 8.x-1.0-alpha2

Git tag 8.x-1.0-alpha2
Bug fixes
New features

Drush 9 support + fix module type

default_content_deploy 8.x-1.0-alpha1

Git tag 8.x-1.0-alpha1
New features

Drush 9 support.

  • drush dcdes exports also path aliases
  • drush dcdes deletes all files in the content directory before saving a new export files
  • Fix loading config directory

default_content_deploy 8.x-1.x-dev

Git branch 8.x-1.x
Subscribe with RSS Subscribe to Releases for Default Content Deploy