Change Details

Bug 14901 was closed because we're now in a much better situation and on the right path, but there's more to do: (Quoting from bug 14901 comment #64) > (In reply to bug 14901 comment 63) > > This patch solves the problem to a certain level, which handles: create, > > delete, move, restore, change. change is the default" > > If the only problem with the patch is that i doesn't resolve the problem > completely, then I quote Nikerabbit "Let's try to get this in and then improve > further as needed". > > For this or any future patch: any log action has a name to show on Special:Log > which is also translatable (unless there is still some very ugly deprecated > method to log), so an easy fallback for the unhandled cases would be to notify > something like "An action of type $log_action has been performed on the page" > etc. A proper and complete fix would require the notification system in core and other core features or extensions to communicate in some way, but that will be another bug. -------------------------- **Version**: 1.21.x **Severity**: major

{T16901} was closed because we're now in a much better situation and on the right path, but there's more to do: (Quoting from bug T16901 comment #64) > (In reply to bug T16901 comment 63) > > This patch solves the problem to a certain level, which handles: create, > > delete, move, restore, change. change is the default" > > If the only problem with the patch is that i doesn't resolve the problem > completely, then I quote Nikerabbit "Let's try to get this in and then improve > further as needed". > > For this or any future patch: any log action has a name to show on Special:Log > which is also translatable (unless there is still some very ugly deprecated > method to log), so an easy fallback for the unhandled cases would be to notify > something like "An action of type $log_action has been performed on the page" > etc. A proper and complete fix would require the notification system in core and other core features or extensions to communicate in some way, but that will be another bug.

Bug 14901{T16901} was closed because we're now in a much better situation and on the right path, but there's more to do: (Quoting from bug 14T16901 comment #64) > (In reply to bug 14T16901 comment 63) > > This patch solves the problem to a certain level, which handles: create, > > delete, move, restore, change. change is the default" > > If the only problem with the patch is that i doesn't resolve the problem > completely, then I quote Nikerabbit "Let's try to get this in and then improve > further as needed". > > For this or any future patch: any log action has a name to show on Special:Log > which is also translatable (unless there is still some very ugly deprecated > method to log), so an easy fallback for the unhandled cases would be to notify > something like "An action of type $log_action has been performed on the page" > etc. A proper and complete fix would require the notification system in core and other core features or extensions to communicate in some way, but that will be another bug. -------------------------- **Version**: 1.21.x **Severity**: major