Extension talk:TitleBlacklist/Archive

Add topic
From mediawiki.org

Using Titleblacklist to block new user creation[edit]

New user regexp not working[edit]

Do you have to set a source in LocalSettings for this extension to use MediaWiki:TitleBlacklist ? I have it set up to block a set of keywords from appearing in new usernames, but it isn't working. 202.33.78.114 09:58, 11 January 2010 (UTC)Reply

Regex[edit]

  1. Documentation says that a Blacklist item "Foo" will be turned into "/^Foo$/usi" - what does usi mean?
  2. It is possible to have real regex support as in UsernameBlacklist?
  3. If not, how can one force a specific pattern to be used, e.g. ^[A-Z][a-z]{7}$, i.e. stop any that does NOT match that pattern?

Time in Russia 13:15, 23 February 2011 (UTC)Reply

  1. usi means "Unicode, singeline, case-insensitive"
  2. What do you mean by real regex?
  3. I'm not sure whether PRCE regex support this. If they don't, file a bugzilla bug. VasilievVV 16:00, 23 February 2011 (UTC)Reply

Solution[edit]

I have edited the Article page which probably addressees both the problems of:

  • Not being able to effect any block of a user name (Titleblacklist looks for "User:" + <newname> e.g "User:Jill Smith"); and
  • How to stop any input that does NOT match that pattern (Block everyone in the blacklist then whitelist the patter you find acceptable).

See the Using Titleblacklist to control user account creation, in the article, for a full explanation.--John Bentley 08:19, 16 May 2011 (UTC)Reply

Can't get URL Blacklist to Work[edit]

I have MediaWiki 1.15.3. I uploaded the extension and added this to LocalSettings.php:

require_once( "{$IP}/extensions/TitleBlacklist/TitleBlacklist.php" );

I then edited TitleBlacklist.php and replaced this:

$wgTitleBlacklistSources = array();

with this:

$wgTitleBlacklistSources = array(
    array(
         'type' => TBLSRC_URL,
         'src'  => 'http://meta.wikimedia.org/w/index.php?title=Title_blacklist&action=raw',
    ),
);

I then try and create a page with a banned word but it doesn't prevent me doing so. What have I done wrong? Holygamer 02:20, 25 May 2010 (UTC)Reply

Automatic updating of blacklist?[edit]

Does this extension automatically update its blacklist periodically, as Extension:SpamBlacklist does? Thanks, Tisane 16:03, 24 March 2010 (UTC)Reply

Not Working[edit]

This extension is failing to work on Zelda Wiki, and when I tried to use it on my test wiki run on my WAMP server, it failed again. I would like to know why it malfunctions, especially when it works on WiKirby.173.168.217.112 22:06, 28 June 2010 (UTC)Reply

Make it work for sysops, as well as users[edit]

Is it possible to blacklist all users from creating pages with matching expressions, including sysops? - Anonymous

Solution: By default it only affects anonymous users. To make it default for all use $wgGroupPermissions['sysop']['tboverride'] = false;. --Subfader 16:52, 6 March 2011 (UTC)Reply

Rules per namespace[edit]

Is there a way to apply a rule for only specific namespaces? --217.251.116.201 17:33, 26 April 2011 (UTC)Reply

  1. We can customize a top banner depending on the ns with w:MediaWiki:Newarticletext.
  2. We can change the background colors and the other CSS settings according to the ns into MediaWiki:Common.css.
JackPotte 18:12, 26 April 2011 (UTC)Reply
what kind of answer is that? It has nothing to do with the question really... --Danwe 00:00, 28 April 2011 (UTC)Reply
This kitten is sooo cute! --Subfader 07:54, 28 April 2011 (UTC)Reply

email blacklist[edit]

Please actual discussion at en:Wikipedia:Village_pump_(technical)#Email_domain_blacklist. Thanks. Regards, mabdul 13:07, 8 November 2011 (UTC)Reply

Mediawiki 1.18.1[edit]

We have found that TitleBlacklist on a japanese language mediawiki will not allow for account creation; It throws a 500 error after clicking the create button.

Same thing on an english wiki:
PHP Fatal error: Call to a member function userCannot() on a non-object in w/extensions/TitleBlacklist/TitleBlacklist.hooks.php on line 86
-- Prod (talk) 20:56, 26 February 2012 (UTC)Reply
Same on mine, would be great if there was a fix.

Allcarwiki (talk)

  • Did you all make sure that you downloaded the appropriate version? This is why you should not use subversion to download unless you are using a development version of MediaWiki. Try downloading an earlier version.Jasper Deng (talk) 02:45, 29 February 2012 (UTC)Reply
  • That seems to have worked, I'm using 1.17 but my mediawiki is 1.18.0. Eh, as long as it works Allcarwiki (talk)

The snapshot generated when selecting "1.18.x" on Special:ExtensionDistributor/TitleBlacklist definitely does not work with MW 1.18.1 - I just tested it on a fresh install and ran into the error mentioned above when trying to create an account. The snapshot generated when selecting "1.17.x" works fine though. 77.190.74.43 00:07, 9 March 2012 (UTC)Reply

still the same problem with yesterday's snapshot and mw 1.18.2 --Richlv (talk) 10:00, 3 April 2012 (UTC)Reply
Exactly same problem today. Works with 1.17.x snapshot on 1.18 install --Iubito (talk) 14:51, 25 May 2012 (UTC)Reply
Try with the latest version (trunk), it works perfectly on 1.18.3 (I think the problem came from a global var, now it has been replaced by a nice singleton) Yannouk (talk) 08:43, 29 May 2012 (UTC)Reply

Regex matching not working[edit]

This is installed on a wiki that I'm a sysop for that used to have dozens of spambot accounts created each day, so I created the following expression to block all usernames longer than 10 characters: ............* <newaccountonly|errmsg>

However, instead of blocking usernames over 10 characters, it's blocking usernames over 4 characters, making it nearly impossible for the very few legitimate users we have to create accounts! I tested it at this site: http://www.spaweditor.com/scripts/regex/index.php so I don't know what's going on, because it works fine there when converted into a full regular expression as per the documentation here. --128.153.222.181 01:27, 17 July 2012 (UTC)Reply

Can anyone help please? The admins have just disabled the TitleBlacklist extension because of this issue and we're back to getting hundreds of bots per day registering! I'm afraid the wiki will become a spam cesspool if this doesn't get fixed, because I have no intention of mindlessly erasing spam every second of every day just to have it re-created a minute later. --128.153.222.181 21:15, 18 July 2012 (UTC)Reply

Difference between Create and Move[edit]

On en, in a WP:VPT topic, I tested the move vs create situations [1]. The move was more strict than the create. Looked odd to me. To me a curiousity, not an issue. -DePiep (talk) 15:53, 11 August 2012 (UTC)Reply

Whitelist "does not work"[edit]

I have a black list with:

.*hotel.* <noedit|errmsg=blacklisted-page>

and a white list with:

Cheap hotel test

But, I'm still unable to create the article "Cheap hotel test". What is wrong? Kelson (talk) 14:00, 14 March 2014 (UTC)Reply

If your filter is not blocking any titles...[edit]

...check the following:

1. If your wiki is case-sensitive, you may be editing MediaWiki:TitleBlacklist. That is a mistake; make sure you're editing MediaWiki:Titleblacklist. Replace the former with a redirect to the latter to prevent this error in the future.

2. If your remote blacklist isn't being fetched, try removing the "s" from "https://". My problem was due to an SSL certificate validation error, and this was the easiest fix (but ideally try to convince curl that the certificate is fine).

--Romanski (talk) 00:58, 9 October 2014 (UTC)Reply

"newaccountonly" confusion[edit]

The newaccountonly attribute is to allow the list to "forbid creation of matching usernames, but allow page creation", but I've just run in to one case where an admin added it to a list entry apparently thinking that it meant "only applies to edits made by new accounts". Would this be clearer if it were named something like accountnameonly? --McGeddon (talk) 10:46, 8 September 2015 (UTC)Reply

What's "new account" supposed to mean in terms of edits? Having less than X edits on the wiki? Account created less than X days ago? That's supposed to be controlled by the autoconfirmed user group. Anyway, even if it would be clearer to have it named differently, that won't be done because would break existing rules. --Ciencia Al Poder (talk) 09:38, 9 September 2015 (UTC)Reply

No documentation for 1.26 or later[edit]

The blurb indicating that the example given here on how to configure this extension no longer applies for 1.26 and up is inscrutable and is not a substitute for actual documentation. If there is somewhere that the "new way" to configure this is outlined, or somebody can throw an existing working example up here to merge into the docs, I'd be more than happy to help. A friend of mine's wiki is currently crippled by spam bots thanks to this change sneaking into the configuration requirements in 1.26.2 --QuasarEE (talk) 16:15, 16 February 2016 (UTC)Reply

Update: Via source diving, I determined that if wfLoadExtension() is used then the global php defines do not exist (they are only defined through the legacy require_once entry point), and the values to be used instead consist of the following:

Old value New value
TBLSRC_MSG 'message'
TBLSRC_LOCALPAGE 'localpage'
TBLSRC_URL 'url'
TBLSRC_FILE 'file'

Log[edit]

Is there anywhere a log (maybe in the server logs) of counts if a rule blocked an page creation? 213.160.30.226 08:45, 11 March 2016 (UTC)Reply

TitleBlacklist incompatibility with GoogleLogin ?[edit]

Hello,

I get this error message when trying to create a new user with TitleBlackliste activated :

Fatal error: Declaration of TitleBlacklistPreAuthenticationProvider::testUserForCreation($user, $autocreate) must be compatible with MediaWiki\Auth\PreAuthenticationProvider::testUserForCreation($user, $autocreate, array $options = Array) in /home/clients/.../web/wiki/extensions/TitleBlacklist/TitleBlacklistPreAuthenticationProvider.php on line 48

Here is the Special version page of my website.

Thanks for any input on how to make it working. DSwissK (talk) 07:54, 22 October 2017 (UTC)Reply

I just got this without GoogleLogin installed. I suppose something is wrong with REL1_31. --[[kgh]] (talk) 16:19, 20 December 2018 (UTC)Reply