Last modified: 2007-01-13 05:25:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10375, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8375 - SpamBlacklist doesn't work on PHP 5.2 ($regexMax too large?)
SpamBlacklist doesn't work on PHP 5.2 ($regexMax too large?)
Product: MediaWiki extensions
Classification: Unclassified
Spam Blacklist (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-12-25 01:10 UTC by anaconda
Modified: 2007-01-13 05:25 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Fixes $regexMax (just 1 line...) (461 bytes, patch)
2006-12-25 01:13 UTC, anaconda

Description anaconda 2006-12-25 01:10:00 UTC
I'm having troubles using the SpamBlacklist extension with PHP 5.2; the error log shows "[error] PHP Warning:  preg_match() [<a href='function.preg-
match'>function.preg-match</a>]: Compilation failed: repeated subpattern is too long at offset 15711 in [blabla]/SpamBlacklist_body.php on line 210". I'm 
not a PHP programmer, but with The Power of Google[tm], it seems caused by a change in the PCRE of PHP. Lowering $regexMax from 20000 to 15694 solves 
the problem (15695 doesn't work).
Comment 1 anaconda 2006-12-25 01:13:56 UTC
Created attachment 2943 [details]
Fixes $regexMax (just 1 line...)
Comment 2 Brion Vibber 2007-01-13 05:25:47 UTC
In r19197 I've reduced the size to 4096. The actual PCRE internal limit seems to
be hard to predict; I think it's a limit on _compiled_ size rather than _input_
size, so input with fancy matching may complicate things.

Hopefully this'll do until we rework the whole rotten thing. :)

Note You need to log in before you can comment on or make changes to this bug.