Last modified: 2014-03-26 13:48:13 UTC
Users with long or complex blog logs may unjustly have this held against them, as the context for entries is limited, and adding additional 1-second blocks to provide comments is highly unsatisfactory. It should be possible to provide a per-user annotation/discussion page for a user's block log. The page would probably be protected in practice (for only admins to edit), but that's not necessary in software. By way of explanation, I did try adding some code https://secure.wikimedia.org/wikipedia/en/w/index.php?title=MediaWiki%3ABlockiptext&action=historysubmit&diff=433164642&oldid=400233851 to MediaWiki:Blockiptext, which would have done the job; but this fell down on not getting the SUBPAGENAME in order to know which page to load. Possibly there is a simple solution which would make the user's name available in that situation. There was discussion https://secure.wikimedia.org/wikipedia/en/w/index.php?title=Wikipedia:Village_pump_%28idea_lab%29&oldid=433348619#Block_log_annotation about implementing in JavaScript, but that's not ideal.
lol, judgmental Wikipedians :P {{SUBPAGENAME}} probably didn't work because the special namespace doesn't have proper subpages. Try {{#titleparts:{{PAGENAME}}|1 |2}} instead. (Which will only work if the user is specified using subpage syntax, instead of url param syntax, but that's true most of the time) Just curious why are you trying to put this on the block a user page, instead of the block log?
Thanks, it works! I was trying to put it on the "Block a user" page because (a) that's where it's most needed and (b) where I thought I could do it without a software change. It would be good to load the same page from the user's block log though. Maybe that can be done in Javascript?
It can't be done currently just by editing system messages (Since you can't tell what the target is from [[mediawiki:Blocklogtext]].) I suppose that message could be changed to accept $1 and $2 as target and user parameters to the log page. Not sure if that's the greatest approach It could be done with Javascript (While anything could be done in js if you wanted.). This is generally the type of thing people prefer not to be done on the client side though (not that that has ever stopped anyone before).
"I suppose that message could be changed to accept $1 and $2 as target and user parameters to the log page. Not sure if that's the greatest approach" - that would seem a reasonably simple solution. What's the downside?
*** Bug 63102 has been marked as a duplicate of this bug. ***
