-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIGx DB content is not being copied #2
Comments
I guess in our processor we could check if MIGXdb is installed and duplicate the appropriate entries in the custom table... |
Sounds great! :-)
--------------------------------------------------------------------
Helloworld Studios Hackenberg & Höfler GbR
Gesellschafter: Fabian Hackenberg, Markus Höfler
Zu den Mühlen 19
35390 Gießen
Mobil: +49 176 610 52372
[email protected]
www.helloworldstudios.com <http://www.helloworldstudios.com/>
… Am 18.03.2019 um 10:22 schrieb Christian Seel ***@***.***>:
I guess in our processor we could check if MIGXdb is installed and duplicate the appropriate entries in the custom table...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AuY9ArSLN9dwlzoMdq1Hdzu_xFXvJc1Uks5vX1q_gaJpZM4b4Qwc>.
|
I don't see, where a onResourceDuplicate is fired in this processors. Looks like the duplicate - processor isn't used here. You will need a way to know, the packagename, the classname and the field, which connects to the resource. Maybe another custom system-event or aftersave - hooksnippet would be nice to have, for doing custom - stuff, after the resource was duplicated |
According to Bruno it needs a customPlugin which is bind to the onResourceDuplicate-Event.
So this plugin could be part of copyContent and is checking if there are any migxdb tables connected to a resource which are then iterated over and copied.
The text was updated successfully, but these errors were encountered: