Last modified: 2011-07-18 16:04:33 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 T31813, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 29813 - Installation: fatal error: PHP's PCRE module seems to be compiled without PCRE_UTF8 support
Installation: fatal error: PHP's PCRE module seems to be compiled without PCR...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.17.x
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-07-11 14:41 UTC by Robin Pepermans (SPQRobin)
Modified: 2011-07-18 16:04 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Robin Pepermans (SPQRobin) 2011-07-11 14:41:24 UTC 
When installing MediaWiki (1.17+, with the new installer) on Sourceforge, it gives a fatal error: "PHP's PCRE module seems to be compiled without PCRE_UTF8 support. MediaWiki requires UTF-8 support to function correctly."

I don't know much about the problem or PCRE itself (maybe this is a Sourceforge-specific problem), but it's possible to install MW 1.16 on Sourceforge, and then upgrading to trunk so it should be possible to install 1.17+ or trunk directly.
Comment 1 Niklas Laxström 2011-07-11 14:47:40 UTC 
The check is there because some stuff* is broken without it.

*Someone else can hopefully clarify what stuff.
Comment 2 Chad H. 2011-07-11 15:04:32 UTC 
Well we use unicode in some of our regular expressions, so we need support for it. If 1.16 installed without checking this then that's the old installer's fault for not being robust enough.
Comment 3 Max Semenik 2011-07-11 16:32:47 UTC 
(In reply to comment #1)
> The check is there because some stuff* is broken without it.
> 
> *Someone else can hopefully clarify what stuff.

Namely, it's used by title and username validation code.
Comment 4 Mark A. Hershberger 2011-07-18 16:04:33 UTC 
INVALID since 1.16 is no longer supported.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links