Used software: FreeBSD 8.3, PHP 5.3.14, PCRE 8.31, Drupal 6.26. When I opening Node Page Wizard I get this error:

warning: preg_match(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1811 in /data/istmat/soft/modules/ctools/includes/cleanstring.inc on line 157.

This is the same error as this one, and patch is the same too:

--- cleanstring.inc.orig        2010-10-18 21:37:03.000000000 +0400
+++ cleanstring.inc     2012-07-23 13:40:58.000000000 +0400
@@ -58,7 +58,7 @@
 '\x{2ce5}-\x{2cff}\x{2d6f}\x{2e00}-\x{3005}\x{3007}-\x{303b}\x{303d}-\x{303f}'.
 '\x{3099}-\x{309e}\x{30a0}\x{30fb}-\x{30fe}\x{3190}-\x{319f}\x{31c0}-\x{31cf}'.
 '\x{3200}-\x{33ff}\x{4dc0}-\x{4dff}\x{a015}\x{a490}-\x{a716}\x{a802}\x{a806}'.
-'\x{a80b}\x{a823}-\x{a82b}\x{d800}-\x{f8ff}\x{fb1e}\x{fb29}\x{fd3e}\x{fd3f}'.
+'\x{a80b}\x{a823}-\x{a82b}\x{e000}-\x{f8ff}\x{fb1e}\x{fb29}\x{fd3e}\x{fd3f}'.
 '\x{fdfc}-\x{fe6b}\x{feff}-\x{ff0f}\x{ff1a}-\x{ff20}\x{ff3b}-\x{ff40}\x{ff5b}-'.
 '\x{ff65}\x{ff70}\x{ff9e}\x{ff9f}\x{ffe0}-\x{fffd}');

After applying this patch error was gone.

Comments

merlinofchaos’s picture

Status: Needs review » Active

No patch attached.

RedRat’s picture

Version: 6.x-1.8 » 6.x-1.9
Status: Active » Needs review
StatusFileSize
new692 bytes

Attached the patch for version 6.x-1.9

kbk’s picture

I'm confused. The OP said applying the patch from #1446372: Invalid Unicode code range in PREG_CLASS_UNICODE_WORD_BOUNDARY fails with PCRE 8.30 fixed the problem but this comment from the same thread indicates "the patches have been committed to all applicable development branches for D6, D7, and D8".

Was the patch applied to the D6 branch or not?

RedRat’s picture

A patch from #1446372 was applied to Drupal core, but ctools module code has the same bug, so similar patch have to be applied to it too.

hansfn’s picture

RedRat’s picture

Yeah, it's the same long standing bug with a different patch. I don't understand why this obvious bug not fixed yet - one way or another.

RedRat’s picture

Version: 6.x-1.9 » 6.x-1.10
Status: Needs review » Reviewed & tested by the community

This bug still exists in the latest release of module... :-(((

DiversiCon’s picture

I can confirm that this bug still exists ctools 6.x-1.10 and the fix suggested in the original post above does work.

neclimdul’s picture

Status: Reviewed & tested by the community » Fixed

committed and pushed.

stevecowie’s picture

Status: Fixed » Patch (to be ported)
StatusFileSize
new1.34 KB

Patch attached that does apply to 6.x-6.10

neclimdul’s picture

Status: Patch (to be ported) » Fixed

Fix has already been applied to the 6.x branch and will be in the next release. I can't apply a fix to an existing release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.