Gaetano Giunta

Step forward in release 5.13: Upserts are now possible, albeit in an impractical way: create a migration with 3 steps: 1. load target item by identifier, with `allow_null_results` and set...

WIP...

In 5.8, the `migrate` command has been made a bit more modular, as parts of it are reused by mass_migrate...

I think I'll push this to version 6

I think that what you are experiencing might be a bug in the eZ kernel, and should be reported in the upstream bug tracker. Of course it is entirely possible...

Ping @SalvatorePollaci any news about this? If you agree this is a kernel bug, I'd like to close this ticket...

Depends most likely on #201

I'd go for having warnings emitted to both Sf log and stdout (the later of course only when migrations are run from the cli)

Wondering if this is actually useful, given that: - the next 'major' version of this (aka TanoConsulting/eZMigrationBundle2) will have a vastly different, incompatible yml migration definition dsl - there are...

This kind makes sense. But it will have to wait for 4.0 to go in, as enabling this means that users might find some new migrations popping up!