CB

Setting a parameter could work when constructing with _getCmsUserObject instead of a private variable.

This will be disabled by default as the typical install should never need it so don't bother with the overhead of parsing for it.

This is partially implemented. We need a cleaner way to do an API store that does field processing. Ideally we need an API store variant of saveSafely so a data array can be provided and field validation/parsing is still done, but it doesn't fail the store due to failed validation. The API variant should only fail at ->bind and ->store which would mean a failed query.

Looks like this is already somewhat supported using $ui of 0. This just needs to go a little further in that $ui 0 won't fail on validation errors, etc.. from plugin behavior.

There's no way to do this cleanly with current APIs without a rewrite to UserTable saveSafely behavior and all field storage behavior as their validation needs to handle API saves.

Proposing this be rejected and instead a new plugin be developed to handle the synchronization.