Change Details

For log actions, CheckUser currently stores the action text in `cuc_actiontext` field in its raw form. Since the action text is generated from the LogFormatter and then inserted, it means CheckUser entries cannot be properly localized and we also cannot format it as needed when displaying to the user. To avoid this, the parameters should be stored in a new field like `rc_params`/`log_params`.

For log actions, CheckUser currently stores the action text in `cuc_actiontext` field in its raw form. Since the action text is generated from the LogFormatter and then inserted, it means CheckUser entries cannot be properly localized and we also cannot format it as needed when displaying to the user. To avoid this, the parameters should be stored in a new field like `rc_params`/`log_params`. As part of this the log ID or other identifier for the log entry in the logging table (or other table) should be stored.

For log actions, CheckUser currently stores the action text in `cuc_actiontext` field in its raw form. Since the action text is generated from the LogFormatter and then inserted, it means CheckUser entries cannot be properly localized and we also cannot format it as needed when displaying to the user. To avoid this, the parameters should be stored in a new field like `rc_params`/`log_params`. As part of this the log ID or other identifier for the log entry in the logging table (or other table) should be stored.