ADmad
ADmad
The only solution I see for this problem is to loop through all dependent associations and disable the trash behavior (or set some flag so that `TrashBehavior::beforeFind()` doesn't add the...
> I could also loop over associations and use setFinder that would set options to include trash and revert it back after delete Yeah that would be inline with the...
Please rebase your branch onto upstream master so that the CI checks can run.
FormHelper::postLink() also generates a form tag with inline style which is hardcoded and there's no convenient way to prevent.
Sometimes CSS libs/devs add some default styling to all inputs which can potentially add spacing around hidden inputs too for e.g.
`id` is not nullable (assuming it's the primary key), so why are you setting it to `null`? This can potentially be caused by having the id field in the form/posted...
You were just lucky that an incorrect usage was silently ignored earlier. Closing this as errors generated by incorrect values set by the user is not an ORM bug.
Support for `insert`/`insertAll` can surely be added, would you like to submit a patch for it?
Yes, sorry, I meant `intersect` and `intersectAll` :)
Please target your pull request to the `5.next` branch.