5.8.0

• New: the content_type/update migration step now accepts the default_always_available element (issue #189)

• New: the kaliop:migration:generate command now accepts a -a flag to allow specifying custom admin users (issue #187)

• Fix: usage of the -a flag when running kaliop:migration:mass_migrate and when running kaliop:migration:migrate -p was not propagated to subprocesses

• Fix: the if element was not giving a fatal error for all migration steps affecting repository elements (Content, Location, etc...), at least for Symfony version 2.7.10

• New: the kaliop:migration:migrate and kaliop:migration:mass_migrate now accept a --force flag that will execute migrations that were previously executed or skipped or failed.
  NB this flag is useful when testing migrations, but should be used sparingly in production context, as replaying migrations that had already been executed can wreak havoc to your database. you have been warned

• BC changes:

  • the kaliop:migration:generate command now uses as default language for the generated migrations the default one of the current siteaccess, instead of 'eng-GB'

5.7.3

• Fix: warnings due to ContentVersionMatcher methods signatures

• Fix: creating migrations for Content creation or update with contents which have empty Image/File/Media fields would crash

Dud release 2

One attempted fix: warnings due to ContentVersionMatcher methods signatures

Dud release

One attempted fix: warnings due to ContentVersionMatcher methods signatures

5.7.0

• New: when manipulating Locations, it is now possible to set references to content_remote_id

• Fix: the migrations generated for content/create and content/update were missing information about section and object states

• New: new migration step: content_version/load. Example:

    -
        type: content_version
        mode: load
        match:
            content_id: 2893941
        match_versions:
            status: archived
        references_type: array
        references:
            -
                identifier: archived_versions_for_2893941
                attribute: version_no
  

• New: migration step: content_version/delete can now match the versions based on status, as well as using complex conditions based on and/or/not

• New: when manipulating content versions, it is now possible to set references to version_no and version_status

• BC changes:

  • migration step: content_version/delete has deprecated the element 'versions' in favour of 'match_versions'

  • when manipulating content versions, it is not possible any more to set references to attributes (might be fixed in the future)

5.6.0

• New: when using step reference/dump, it is possible to use a custom label instead of the reference name

• New: when creating array references, it is possible to allow them to be empty without this being considered an error.
  Ex:

            ...
            references_type: array
            references_allow_empty: true
            references:
                -   identifier: my_content_ids
                    attribute: content_id
  

• New: the classes which implement MigrationGeneratorInterface will now receive the whole step definition as part of the $context parameter for the generateMigration call. This allows them to tailor the generated migration definition based on custom conditions.

5.5.1

• New: when updating, deleting, loading Contents and Locations, you can now sort the results, as well as use an offset and limit. Ex:

    -
        type: content
        mode: load
        match: { content_type_identifier: folder }
        match_offset: 0
        match_limit: 10
        match_sort:
            - { sort_field: published, sort_order: desc }
  

• New: it is now possible to generate migration definition files via migration steps.
  Also, more references are resolved in migrationdefinition/generate steps.

• New: it is now possible to set the location remote_id when creating locations
  Also, more references are resolved in location/create and location/update steps.

• New: it is now possible to match users using their group id

• New: it is now possible to match user groups using the parent group id

5.5.0

See 5.5.1

5.4.1

• fix: when a sub-migration is skipped in a step of a loop, do not halt he loop immediately but go on until the end
• fix: references are now resolved for the "over" element of loops

5.4.0

• Fix: changing ContentTypeGroup upon updating ContentType

• Fix: setting custom modification date on Content Create (ticket #173)

• New: it is now possible to create or update a Content setting multiple translations at the same time. Ex:

    -
        type: content
        mode: create
        content_type: myClass
        parent_location: 2
        attributes:
            title:
                eng-GB: hello world in eng-GB
                abc-DE: hello world in abc-DE
  

  Note that in order for the content definition to be considered valid "multi-langauge", ALL attributes values must
  be specified using a language key. The following example is thus invalid:

        attributes:
            title:
                eng-GB: hello world in eng-GB
                abc-DE: hello world in abc-DE
            description: A description to rule them and in the drakness bind them
  

• New: it is now possible to use Symfony Expression language in IF conditions. Ex:

    -
        type: ...
        if:
            "reference:some_id":
                satisfies: "value % 3 == 0"
  

  Here the migration step would only be executed if the Id stored in the reference is divisible by 3.

• New: it is now possible to loop over arrays, achieving the same as a php foreach call. Ex:

    -
        type: loop
        over: { "hello": world, "buongiorno": mondo }
        steps:
            -
                type: reference
                mode: set
                identifier: loopref
                value: "We have found key: [loop:key] and value: [loop:value]"
                overwrite: true
  

  This should be useful f.e. in conjunction with references of type array, introduced in version 5.1