Features features features!

• New: allow the generate command to easily create a migration definition in a custom directory instead of a bundle

• New: allow the position field for attributes in ContentType create migrations.
  NB the algorithm used for the sorting of ContentType fields has changed compared to previous versions, for both creation and update:

  • mixing fields with a specified position and without it results in the fields without position to always go last
  • for consistent results, it is recommended to always either specify the position for all fields or to none
  • the eZ4 Admin Interface does not display the actual field position, and shows 10,20,30 instead... In order to
    see the real position that fields currently have it is recommended to generate a ContentType create migration

• New: better support for content fields of type ezmedia:

  • it is now possible to put the binary files next to the migration file, in a subfolder named 'media', similar to what was already possible for ezimage and ezbinaryfile
  • the attributes to be used in the migration yml to define an ezmedia field are more consistent with the others
  • the path to the media binary file in generated migrations has become an absolute path

• New: it is now possible to update Content Type Groups

• New: when creating a Content Type Group, it is possible to set a custom creation date

• New: it is now possible to generate migrations for Sections, Object States, Object State Groups and Content Type Groups

• New: it is now possible to set references to many more attributes when creating/updating Contents: content_id, content_remote_id, always_available, content_type_id, content_type_identifier, current_version_no, location_id, main_language_code, modification_date, name, owner_id, path, publication_date, section_id

• New: it is now possible to set references to many more attributes when creating/updating Locations: location_id, location_remote_id, always_available, content_id, content_type_id, content_type_identifier, current_version_no, depth, is_hidden, main_language_code, main_location_id, main_language_code, modification_date, name, owner_id, parent_location_id, path, position, priority, publication_date, section_id, sort_field, sort_order

• New: two new migration steps are available: content/load and location/load.
  Their purpose is to allow to set references to the attributes of the loaded objects. This way it is f.e. possible
  to copy the section from one content to another

  -
      type: content
      mode: load
      match:
          remote_id: firstcontent
      references:
          -
              identifier: section_ref
              attribute: section_id
  -
      type: content
      mode: update
      match:
          remote_id: secondcontent
      section: "reference:section_ref"
  

• New: it is now possible to manually create references, including both bulk loading from file and getting the value from configuration parameters (useful f.e. to manipulate different contents based on environment).
  It is also possible to dump the resolved reference values for debugging purposes.
  Details in the dedicated documentation

• New: the generate command can be used to generate SQL migrations in YML file format

• New: SQL migrations in YML file format can set references to the number of affected rows

• New: the migrate command now accepts short-version for all options

• New: an assert step is available to validate migrations used by the test suite

• Improved: make it easier to run the test suite outside of Travis and revamp test instructions

• Fix: content creation from the generate command would fail if a field of type Relation has no value

• Fix: section updates would fail at setting the name

• Fix: 'match all' would fail for Object States

• Fix: properly resolve references in match conditions when these are specified using nested conditions with AND and ORs

One feature, une bugfix

• Added a new event: ez_migration.migration_aborted that can be listened to by user code, triggered when a MigrationAbortedException is thrown by a migration executor
• Fix BC with custom Complex FieldType handlers created by extending the bundle (bug introduced in 3.2)

Exciting new features; improvements in migrations generation

• Fixed: on content creation, assigning a section by identifier instead of id
• New: allow setting section upon UserGroup creation and update
• New: when setting a value for a 'selection' content field, it is now possible to use the selection string value instead of its numerical index; it is also possible to use a single index/name instead of an array
• New: when using the generate command for content creation migrations, 2ndary locations are exported. Also, the sort field and sort order of the main location are exported
• New: it is now possible to use a specific type of exception during execution of a Migration Step (or a listener) to abort a migration without having it flagged as failed - it can be flagged as either done or skipped
• New: it is now possible to create/update/delete sections via migrations
• Improved many error messages

Fix usage of 'lang' parameter in 'generate' command

Also better docs for the settings available in creation of ContentTypes

Better matchers, migration generation and user/group creation

New features in this release concern 3 areas:

• it is now possible to use 'all', 'and', 'or', 'not' in the match conditions used to select entities to update/delete
• usage of remote_id and references is expanded in creation/update of Users and UserGroups
• it is now possible to use the generate command to generate a slew of migrations: Content and ContentType creation, update and deletion. This begins the path allowing the bundle for backups and site migrations. NB: this feature is to be considered in beta state for this release.

More details in the WHATSNEW file.

Special thanks to contributors @blankse and @andesk.

Improve support for eZTags and eZPlatform

Changes since 3.0.3:

• Support 'default_always_available' in content type definitions
• Add remote_id property and reference resolution for parent_tag_id property in tag creation
• Better compatibility with eZPlatform when matching Contents by Content Type

2 bugfixes

• Fix handling of relation list attributes which are not references
• Avoid sql warning due to long execution error messages

Better support for timestamps in content creation/modification dates

3.0.2

better docs for role management

Two small fixes

• Fixed: reporting of errors with creation of roles with a SiteAccess limitation
• Improved: reduce the chances of mysql deadlocks when running migrations in parallel

Christmas is coming!

The list of new features, bugfixes and changes, compared to the latest stable version 2, are too long to be listed here.

You can find them in the release-notes document at: https://github.com/kaliop-uk/ezmigrationbundle/blob/master/WHATSNEW.md

Compared to version the latest beta version 3.0.0-beta6, the changes are:

• fixed issue #84 : better error messages when content does not validate
• allow NULL as value for all field types for content creation/update
• allow creation and deletion of content type groups
• allow more flexibility in xml/richtext reference resolving
• allow eztags deletion
• at content creation, use default child sorting from content class definition if unspecified
• merge non-intrusive bits of PR #81
• refactored reference resolvers to use matchers
• improved documentation