The main difference is that entitysync is a lot simpler and lighter than the deploy module; all the configuration happens on Rules level - apart from the generic settings (shared secret, encryption settings in the future).
There are plenty of minor ones also, but the thing is that it has only one job and the aim is to do it well.
In case you are wondering the aim is to share entities between Drupal installations.
That said, I would recommend entitysync to people who like modules that *just work*.
Same question as Adam:
I have identical content types/fields on both sites (same machine names as well). When I sync, the data shows up in the wrong content type. How can I fix this? Thanks!
Comments
Comment #1
tcmug commentedI'm glad you asked :)
The main difference is that entitysync is a lot simpler and lighter than the deploy module; all the configuration happens on Rules level - apart from the generic settings (shared secret, encryption settings in the future).
There are plenty of minor ones also, but the thing is that it has only one job and the aim is to do it well.
In case you are wondering the aim is to share entities between Drupal installations.
That said, I would recommend entitysync to people who like modules that *just work*.
Comment #2
niccolox commentedwell, if Entity Sync actually works, that would make it different to Deploy
Comment #3
adamgerthel commented@niccolo :)
@tcmug When syncing entities, does it assume that the content types (for example) on the different sites use the exakt same field setup etc?
Comment #4
allsite commentedSame question as Adam:
I have identical content types/fields on both sites (same machine names as well). When I sync, the data shows up in the wrong content type. How can I fix this? Thanks!
Comment #5
milos.kroulik commented@allsiste: Are you still using this module? If so, you should post mentioned bug to separate thread.