log_params should contain the revision IDs of null revisions created by log events.
Version: 1.24rc
Severity: normal
log_params should contain the revision IDs of null revisions created by log events.
Version: 1.24rc
Severity: normal
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | GeoffreyT2000 | T72518 Tags for page moves should apply to auto-generated edits | |||
Open | None | T70950 rc_this_oldid (resp. log_params) should contain revision ID of null revision (resp. redirect) created by moves | |||
Resolved | Cenarium | T127852 Publish of recent change for a log entry should be deferred | |||
Resolved | Cenarium | T127848 Should be possible to associate a revision to a log entry without making it unpatrolled | |||
Open | None | T70936 rc_this_oldid should contain the revision IDs of null revisions created by log events | |||
Resolved | Cenarium | T11501 Make file uploads patrollable | |||
Open | None | T98617 Make page moves patrollable | |||
Resolved | Cenarium | T122089 Log entries and associated page revisions are not actually associated in the database |
What about the possibility of storing this data in rc_this_oldid and rc_last_oldid? Is there any reason to have those fields be 0 for log events?
This should make it possible to add an explanatory error message when attempting to undo/rollback/reject a move, see T6433.