The special page was rewritten in MediaWiki 1.23 to make it usable on
wikis the size of Wikipedia (commit 87be24db /
https://gerrit.wikimedia.org/r/#/c/110299/ and some follow-up changes).
Unfortunately this optimization for massive wikis seems to have caused the
performance to suffer on sm
George, can you send me a few of those abuse filters which have slowed down
the spam bots for you?
Thanks.
___
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
HI Chris
I was supporting a general position of Boris about the validity of some
needing access control. I currently use SemanticACL so I can use restrict
access on a per-page basis to a self-defined group within a page. It makes
project management easier and it helps when that "page" group doesn'
On Tue, Jan 27, 2015 at 5:26 PM, Chris Tharp wrote:
> I agree completely with Boris about access control. Only with a combination
> of Two extensions: Lockdown and SemanticACL have I ever been able to get to a
> reasonable level of access control that I desired for my wikis.
Chris, other than t
Hello Jakub,
> "You are viewing a cached version of this page, which can be up to 29
days, 23 hours and 40 minutes old."
to fix it temporarily, you could run this script (from maintainance dir)
updateSpecialPages.php
Erkan YILMAZ
On Wed, Jan 28, 2015 at 7:04 PM, Jakub Klinkovský wrote:
> Hi,
Hi,
since the update of MediaWiki from 1.22 to 1.24, which happened about 10 days
ago [1], ArchWiki has some problems with the Special:ActiveUsers page [2]:
* The number of users in the list is much lower than it should be according to
the Special:Statistics page.
* The users in the ActiveUsers
I sysadmin a few internal and one external wiki at work, and also
rationalwiki.org. One of the work wikis is SMW.
For the work wikis, OH GOD I WANT VE. Our users are normal competent
people who aren't so good with computers. But they can work a
word-processorish rich text editor just fine. For thi
>what should we actually focus on?
VisualEditor. Do everything to ease/encourage contributing content. Having
to install node.js is far too complicated. Could node.js be a requirement
for the web host to qualify as supporting MediaWiki?
Shadow namespace to include Template, Module, Help, etc. name
