Last modified: 2012-04-16 09:15:48 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 T28297, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26297 - Check for PCRE UTF8 support in the installer
Check for PCRE UTF8 support in the installer
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-10 12:21 UTC by Bryan Tong Minh
Modified: 2012-04-16 09:15 UTC (History)
1 user (show)

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


Attachments

Description Bryan Tong Minh 2010-12-10 12:21:44 UTC
Some users appear to have a PCRE that does not support utf8. This causes among others problems like "Warning: preg_replace() [function.preg-replace]: Compilation failed: this version of PCRE is not compiled with PCRE_UTF8 support at offset 0 in includes/Title.php on line 2285". The installer should explicitly check for this, rather than failing with a nasty PHP warning.
Comment 1 Chad H. 2010-12-10 12:24:07 UTC
(In reply to comment #0)
> Some users appear to have a PCRE that does not support utf8. This causes among
> others problems like "Warning: preg_replace() [function.preg-replace]:
> Compilation failed: this version of PCRE is not compiled with PCRE_UTF8 support
> at offset 0 in includes/Title.php on line 2285". The installer should
> explicitly check for this, rather than failing with a nasty PHP warning.

I believe Installer::envCheckPCRE() handles this :)
Comment 2 Bryan Tong Minh 2010-12-10 12:29:02 UTC
Is that new in 1.17?
Comment 3 Chad H. 2010-12-10 12:33:42 UTC
(In reply to comment #2)
> Is that new in 1.17?

Of course :p
Comment 4 Bryan Tong Minh 2010-12-10 12:34:58 UTC
Ok :)

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


Navigation
Links