MediaWiki talk:Content-not-allowed-here

Protected edit request on 28 February 2019
Move User:Pppery/MediaWiki:Content-not-allowed-here to MediaWiki namespace without leaving a redirect.

(Background: Edit filter noticeboard ) This message displays when attempting to move a module out of the module namespace. For users likely to do that, the error message displayed is pure technical gobbledygook. I request that a clearer error message (based on MediaWiki:Abusefilter-warning-scribunto-contentmodel be introduced for this specific case to reduce confusion. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 01:28, 28 February 2019 (UTC)
 * I wish I could find some more centralized place to put this request, but there doesn't seem to be one due to the scant onwiki documentation of content models. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 01:28, 28 February 2019 (UTC)
 * &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 13:25, 28 February 2019 (UTC)
 * I don't think this message should mention the edit filter, as it's actually hardcoded MediaWiki restriction. Suffusion of Yellow (talk) 20:41, 28 February 2019 (UTC)
 * As currently coded in my userspace, it doesn't. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 20:42, 28 February 2019 (UTC)
 * See the title text for the image. Suffusion of Yellow (talk) 20:46, 28 February 2019 (UTC)
 * D'oh! In any case, you could have just fixed that yourself (or make any other tweaks) yourself instead of pinging me about it. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 20:49, 28 February 2019 (UTC)
 * Sorry, didn't know if you wanted me messing with your userspace. Suffusion of Yellow (talk) 20:50, 28 February 2019 (UTC)


 * ❌ See examples below. The requested change ends up stripping off useful information, adding an extra box and picture that aren't really needed here.  The current message is very "clear" about exactly what is wrong, and the new message isn't exactly accurate, the problem is specifically with the content model not the leaving namespace - and this message could be reused in the future, so hardcoding assumptions in to it can set us up for future inaccuracies as well. —  xaosflux  Talk 14:05, 5 March 2019 (UTC)


 * Current error example:


 * New error example: