Last modified: 2014-03-19 09:54:05 UTC
There is currently no way to have the following messages blank (in all likelihood, all messages are similarly affected): excontent excontentauthor exblank exbeforeblank With the introduction of the MediaWiki:Deletereason-dropdown, there is little or no need for these automatic reasons. Having them blank should be an option regardless.
(In reply to comment #0) > (in all likelihood, all messages are similarly affected) All messages that are treated as wikitext can be easily blanked by just changing them to <!-- This message is empty on purpose -->
For these messages (at least), such a comment (along with or anything else I've tried, including __END__) gets put into wpReason as a literal string. A single space results in MediaWiki using the default message.
(In reply to comment #1) > (In reply to comment #0) > > (in all likelihood, all messages are similarly affected) > All messages that are treated as wikitext can be easily blanked by just > changing them to <!-- This message is empty on purpose --> > Unfortunately, these messages are NOT treated as wiki text and instead are treated as literal strings, no matter what gets put into them. I browsed around the source but I can't seem to find why having an empty message or a message containing a single space are going back to being the default message in these instances. I'm assuming all messages that are interpreted this way (literal strings that are used to auto populate input fields of forms) have the same issue as well.
All messages fall back to the default value when the page is blank. These particular messages are not meant to be blank.
*** Bug 16493 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > All messages fall back to the default value when the page is blank. > > These particular messages are not meant to be blank. > Given that there seems to be support to allow this, I'm re-opening.
Isn't this about $wgUseAutomaticEditSummaries?
No, that variable controls *edit* summaries, not things like this. At least I can't see anywhere in source for the delete autoreasons to be affected by that variable.
The general standard is putting "-" into a UI message to blank it, but this requires explicit support from the code that creates that element. r44127 should handle this; Article::generateReason() (the internal function which creates these autosummaries) will now return a blank string if the message came out as '-'.
