Closed (fixed)
Project:
Replicate
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Dec 2014 at 14:57 UTC
Updated:
11 Oct 2016 at 19:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
btopro commentedMakes sense to me, minor API addition / flexibility that would allow for things like entities that have direct relation (such as book / OG) being replicated and related to replicated parents correctly / allow for replication chaining
Comment #2
vbouchetI agree that would add some flexibility. However, I am not sure using drupal_alter() is the best approach as we basically don't alter anything but only give the opportunity to act on related "things". module_invoke() is probably a better approach from my point of view.
Comment #3
jgalletta commentedAdded a hook and modified the api file to explain how to use it. Tell me what you think about it.
Comment #4
btopro commentedlooks reasonable; if we have an entity and it's just been replicated, then allow stuff to fire
Comment #6
jgalletta commentedComment #8
chrisrockwell commentedIf you can't use -dev version of this, replicate_entity does return the new id.
Pardon my ignorance here, but is there somewhere we can track what is stopping -dev from graduating? Edit to be more clear: If you can point me to the issues that are preventing dev from graduating, I'll see if I can help with any of them.