Sun, Mar 15
Custom togglers are very useful when used properly (example). I think the best solution, which is also the easiest one in this case, is to use the same scheme for regular togglers and custom togglers. It's trivial to use the same default toggleARIA flag (true for both).
Wed, Mar 11
Mar 10 2020
Nov 30 2019
Thanks, @Urbanecm provided solution to the robots.txt issue.
Nov 27 2019
Yep, now it works :) Thanks again!
It seems I don't have permission for the "REQUEST INDEXING" tool.
Thanks a lot, John!
Nov 24 2019
I prefer setting no time limit. This is administrative task for the project, so access is required as long as I'm an administrator at the Hebrew Wikisource. If definite time limit is required, let's say three years, and renew access when expired.
Nov 20 2019
Nov 15 2019
Let's get one step at a time. Before getting into legal and technicality, WMF should assess and approve the request.
Nov 13 2019
Nov 12 2019
Apr 28 2019
Aug 5 2018
In theory, redirects may increase the total number of pages by an order of magnitude. However, in practice, the average number of redirections per page is relatively small. For example, in my project a lot of pages have multiple redirections (alternative spelling and such). The total number of pages in the project category is 1190. The total number of pages including redirections is about 2000.
Jul 29 2018
I guess a nice warning should be sufficient for now.
Jul 24 2018
Oct 26 2017
I can confirm a regression in the Massviews tool. You can easily reproduce the problem by setting range = latest-1. The tool will stop when "processing page X of Y", where Y−X are the number of pages with no stats. Note that when a page has no stats, that is, zero pageviews for the given range, the API returns a 404 error.
Oct 22 2017
Is there any workaround to force recount for a given category?
Oct 18 2017
Feb 22 2017
Thank you @MusikAnimal for the fast fix!
Feb 19 2017
Nov 28 2016
Edit notices reside in the MediaWiki namespace because all other user interface text lives in the MediaWiki namespace.
Editnotices are the edit-page counterparts of notice templates. A nicer solution is to implement editnotices via template inclusion. It's not possible with current design.
Nov 27 2016
Nice, I should have thought about it... :) 10nx!
Nov 26 2016
Following @Bawolff notice, I'm including brief info on the [[s:he:user:OpenLawBot | OpenLawBot]] in hewikisource.
The OpenLawBot is the the background process of the [[s:he:ספר החוקים של מדינת ישראל | Israeli Book of Laws' project]] in the Hebrew Wikisource. It provides the legal textbook of the State of Israel (laws, ordinances, regulations, decrees, etc.), in a readable manner, with interlinks between the legal documents. Each OpenLaw page is composed of two pages – the source text, stored at NS:116 (see T66353), and the formatted wiki text, stored and displayed at the main NS. The source page contains the actual legal text in a simplistic format, very easy to understand and edit. The wiki page contains a formated text derives from the source text, after sophisticated automatic editing. It is very complex due to the usage of templates for the visual presentation. The bot is making editnotices for each new article in order to prevent new users from trying to update the wiki (formatted) part of the text. The editnotice directs the user to the source text.
Feb 17 2015
This is a technical issue, and there is a consensus it's worth trying to use Microdata attributes, as there's no cost.
Nevertheless, following your comment above, I asked at the Scriptorium for more votes on the request.