I run ShoutWiki's Customer Support Team, but in addition to that, I also work on the various MediaWiki-related things we at ShoutWiki use.
- User Since
- Aug 19 2014, 12:44 PM (230 w, 6 d)
- MediaWiki User
- Jack Phoenix
Sep 19 2017
Jul 6 2017
Firstly, is this the right place to make this request?
Yup, this works. Alternatively you can also email us, either via Special:Contact or directly (firstname.lastname@example.org) for private matters.
Jun 21 2017
On the other hand, this extension is used on (select) WMF wikis, such as Wikimedia Commons, so it's code-reviewed and guaranteed to be compatible with recent versions of MW.
However, we have a very similar extension -- HAWelcome -- already, which supports SocialProfile, which NewUserMessage doesn't. (See also T68)
Jun 8 2017
The steward group was historically created (on ShoutWiki) as a way "to deal w/ rouge admins", to quote what Pinky wrote on GlobalSettings.php many, many moons ago. As such, I'm not sure about this request. Yes, this is a request we hear more often than once a year or so, but I think we can continue dealing with these requests on a case-by-case basis and focus on getting AdminPanel into shape so that admins (etc.) are able to change the wiki's default skin, theme and such stuff without having to contact staff. That seems more beneficial for all parties IMO.
Mar 29 2017
Pretty much, yeah, although I'm not sure if the patch has been tested on wikis running both extensions. I think the reason I was keeping this open was due to my earlier comment about merging AutomaticBoardWelcome and HAWelcome, but we can create a separate task for that or something.
Mar 4 2017
Mar 3 2017
The logo and the drop-down menu are separate features. The drop-down menu is controlled by MediaWiki:Refreshed-wiki-dropdown and its syntax is documented on MediaWiki.org. If it's empty (the default), the little "arrow" next to the wiki's wordmark won't be shown.
The actual site logo is configured by MediaWiki:Refreshed-this-wiki-wordmark (for desktop/normal screen resolutions) and MediaWiki:Refreshed-this-wiki-mobile-logo (for mobile/smaller screen resolutions); see the documentation for details.
Feb 27 2017
Feb 16 2017
Feb 7 2017
With the DeleteWiki improvements done in rSHWK4107 this is no longer an issue.
We've been running MW 1.28 since 16 December 2016, so this can be safely closed.
Feb 5 2017
Jan 15 2017
This should now be fixed for good (ditto for T155).
There are four gradient-* images in /skins/Aurora/resources/images, and four respective CSS rules in /skins/Aurora/resources/aurora.css which use 'em:
- gradient-body.png (CSS rule which uses this: #content-inner)
- gradient-footer.png (CSS rule: #foot)
- gradient-header.png (CSS rule: #head)
- gradient-input.png (CSS rule: #full-search)
Jan 14 2017
Dec 21 2016
Actually, as per the official release notes I quoted previously, that's intentional: Their usage is discouraged, but if they are manually enabled, a tracking category will be added to help identify usage and make it easier to migrate away from.
Yep, seems that what the MediaWiki.org manual page forgot to mention that caches need to be cleared after changing the value of the setting. I've manually flushed the cache for Rose-Biblio's main namespace, so now this issue should be properly resolved. :)
Dec 20 2016
This is an intentional behavior change in MediaWiki 1.28. To quote the official release notes:
Dec 17 2016
Long story short, SpamRegex is intentionally very restricted because unlike AbuseFilter and whatnot, it is a global tool. If it were administrator-viewable (let alone editable!), that probably wouldn't go so well because all you need is a valid email address to create a new wiki.
Dec 16 2016
Besides that, as far as I've seen, global help: pages have worked as intended, save for that redlink issue, which should be now fixed.
Dec 8 2016
Nov 19 2016
Nov 16 2016
Nov 15 2016
@CJC fixed this a while ago, CW has recently been updated so there's nothing else to be done here.