@BigProf:
Apart from problems* which seem to occur from time to time when cURL-cloning sub-records:
We should get more influence over the new data set that is created when duplicating.
I suggest that we should get a new hook function
TABLENAME_before_duplicate(&$data, $memberInfo, &$args) : bool for this, in which we can change
$data according to our own requirements.
This would have the following advantages:
- We can modify any field, for example build custom unique id's, update timestamps, make use of currently logged in user etc.
- We could prevent duplication by returning
FALSE.
- We could set certain values that we could evaluate in the
_after_insert hook, later on.
- It remains 100% backwards compatible: if this hook function does not exist, everything remains in the standard
As an alternative
AppGini could give us some extra info in
$args-array for us to see if this is a (new/blank) insert or a record-duplication.
---
Note to myself
In
before_insert-hook we can check for any data, breaking constraints, and then change
$data accordingly before AppGini inserts it. Also, we can return
FALSE there to deny insert.
---
* I know, this will not solve the issue reported here.
AppGini plugins to add more power to your apps:
