Wikisource:Administrators' noticeboard

From Wikisource
Jump to: navigation, search
Administrators' noticeboard
This is a discussion page for coordinating and discussing administrative tasks on Wikisource. Although its target audience is administrators, any user is welcome to leave a message or join the discussion here. This is also the place to report vandalism or request an administrator's help.
  • Please make your comments concise. Editors and administrators are less likely to pay attention to long diatribes.
  • This is not the place for general discussion. For that, see the community discussion page.
  • Administrators please use template {{closed}} to identify completed discussions that can be archived
Report abuse of editing privileges: Admin noticeboard | Open proxies
Wikisource snapshot

No. of pages = 2,249,664
No. of articles = 637,864
No. of files = 20,222
No. of edits = 7,127,593


No. of pages in Main = 378,001
No. of pages in Page: = 1,532,258
No. validated in Page: = 345,294
No. proofread in Page: = 463,013
No. not proofread in Page: = 572,153
No. problematic in Page: = 27,236
No. of validated works = 2,687
No. of proofread only works = 1,346
No. of pages in Main
with transclusions = 166,739
% transcluded pages in Main = 44.11
Σ pages in Main


No. of users = 2,826,567
No. of active users = 338
No. of group:autopatrolled = 448
No. in group:sysop = 31
No. in group:bureaucrat = 3
No. in group:bot = 21


Checkuser requests[edit]

  • Wikisource:checkuser policy
  • At this point of time, English Wikisource has no checkusers and requests need to undertaken by stewards
    • it would be expected that requests on authentic users would be discussed on this wiki prior to progressing to stewards
    • requests by administrators for identification and blocking of IP ranges to manage spambots and longer term nuisance-only editing can be progressed directly to the stewards
    • requests for checkuser

Notice of checkuser action[edit]

In accordance with your local checkuser policy, I'm writing here to let you know that I've just checked and locked some wp0 abusers/spammers on this wiki. Regards, RadiX 20:12, 29 October 2017 (UTC)

Bureaucrat requests[edit]

Page (un)protection requests[edit]

Other[edit]

Resource Loader issue needs outside guidance[edit]

The more I read up on this RL change and the subsequent actions needed (or taken?), the more I get the feeling some of my approach to site wide & gadget .js/.css organization over the months is going to behind this week's latest problems. If that winds up to be the case, then I'm truly, truly sorry for that. Let me try to document those steps and the reasoning behind them in hopes someone (@Krinkle:) can made sense of our current state and put us on the right path post RL change(s).

Originally, we not only had a ridiculous amount of scripting and .css definitions in our primary site-wide MediaWiki files to begin with but also called a number of stand-alone .js/.css files within those primary MediaWiki files called unnecessarily in addition to calls to various sub-scripts on top of any User: selected gadgets being called -- some of which eventually became default loaded per concensus, etc..

A simple depiction of the key files mentioned minus any Gadgets basically went like this...

Over several months with help of other folks, I began to consolidate and/or eliminate as much scripting calls as I could -- creating optional Gadgets whenever possible -- and tried much the same for the .css class definitions. The rationale behind doing this can be found in several places, most importantly: Wikipedia. The premise to keep the MediaWiki site-wide files "lean" goes like this....

 /**
 * Keep code in MediaWiki:Common.js to a minimum as it is unconditionally
 * loaded for all users on every wiki page. If possible create a gadget that is
 * enabled by default instead of adding it here (since gadgets are fully
 * optimized ResourceLoader modules with possibility to add dependencies etc.)
 *
 * Since Common.js isn't a gadget, there is no place to declare its
 * dependencies, so we have to lazy load them with mw.loader.using on demand and
 * then execute the rest in the callback. In most cases these dependencies will
 * be loaded (or loading) already and the callback will not be delayed. In case a
 * dependency hasn't arrived yet it'll make sure those are loaded before this.
 */

The result of that effort as it stands today can be depicted basically like this....

The predominant change in order to move towards the previously cited rationale & approach is that the bulk of the scripting and class definitions now reside in the default-enabled Site gadget files, MediaWiki:Gadget-Site.js & MediaWiki:Gadget-Site.css. And by no means is the current state the desired final approach; its been a work in progress as time allowed over several months.

Obviously, now with the recent change to Gadgets and ResourceLoader, either the existing rationale or my attempts (or both) are no longer in harmony -- if they ever were. In my view, we need someone like Krinkle (or maybe the collective minds of Wikitech-l?) to take the time and attention needed to come in here and straighten all this out -- one way or the other. My gut tells me THAT will resolve the reported loss of one thing or another post-RL change(s). Again, if I'm right about my actions exacerbating problems for other, I apologize and take full responsibility. -- George Orwell III (talk) 20:54, 8 August 2015 (UTC)

I've made a few minor changes in addition to yours that hopefully make things work a bit more like you intended. I'm happy to provide further guidance but that probably works better for a more specific need or question. Perhaps bring it up on Wikitech-l or on IRC so we I can help you move forward with any unresolved issues. Krinkle (talk) 21:37, 20 August 2015 (UTC)

Transclusion display change — right margin[edit]

I am looking at some transcluded chapters, eg. Chartism/Chapter 10 and I see that we now have an indented right margin (~90%???) and full formatting rather than left formatting (jagged right edge). Has someone made a local change or have we inherited something along the way? — billinghurst sDrewth 21:56, 14 March 2016 (UTC)

@George Orwell III: do you know where this has occurred? I cannot see local change, and then working out where the formatting occurs is unknown to me. — billinghurst sDrewth 21:59, 17 March 2016 (UTC)
Perhaps something similar with this left margin which was not on my user's page and appeared recently without my knowing how or why? I've had a similar surprise on the French wikisource too. --Zyephyrus (talk) 01:27, 18 March 2016 (UTC)
For whatsoever this is worth (probably not much) this "change" in the right margin is most definitely (Java)Script driven rather than a CSS change (load the page with javascript disabled: result renders fine without restriction on right margin.) I think I may have gotten to the bottom of this although I'll leave others to add the reasoning for why the changes were made:
  • MediaWiki:Gadget-Site.css has specified a right-margin of 3em forever (well since at least May, 2015 which is as far back as I have checked)—per
    body.ns-0 div#regionContainer {
    	position: relative;
    	display: block;
    	box-sizing: border-box;
    	margin-right: 3.00em;
    	margin-left: 3.00em;
    }
    
  • MediaWiki:PageNumbers.js has attempted to enable the above since forever but using buggy code which appears to have been "fixed" in this change on 1st January, 2016.
The net result is as observed, at least as far as English wikisource is concerned. AuFCL (talk) 04:20, 18 March 2016 (UTC)
Thanks. The issue for me is the header template now is wider than the body component, so when items are centred in both, there is no alignment it looks buggy to my eyes. Does that also explain the fully justified page formatting, rather than the left alignment? — billinghurst sDrewth 06:13, 18 March 2016 (UTC)
Pardon. I understood the "okay with frown" part: I was only reporting the status quo as I observe it: with the expectation it might give the appropriate users the sensitive points at which further change might best be implemented should they (you?) so choose. However I completely fail to understand your comment and thus cannot help further. AuFCL (talk) 06:44, 18 March 2016 (UTC)

Disable Dynamic Navigation Bars by default[edit]

I’ve cleaned up the remaining NavFrames, so this gadget is no longer needed for the majority of users. It might be kept in order to make it possible to watch old page versions, but it’s not important enough to slow down Wikisource for everyone. --Tacsipacsi (talk) 17:23, 30 October 2017 (UTC)

Anyone? --Tacsipacsi (talk) 16:01, 24 November 2017 (UTC)
Sure, sounds good to me. —Beleg Tâl (talk) 02:22, 25 November 2017 (UTC)