WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

#3887 closed defect (bug) (invalid)

After upgrading to php-5.2.1 i get a random error in server-log mentioning formatting.php

Reported by: overrider88 Owned by:
Milestone: Priority: low
Severity: normal Version: 2.1.1
Component: General Keywords: formatting.php php5.2.1
Focuses: Cc:

Description

Hi,

System:
FreeBSD 6.2
Wordpress 2.1.1
Apache13+modssl+mod_mysql
PHP 5.2.1 with Suhosin-Patch 0.9.6.2 (cli)
mysql 5.0.33

Problem:
While clicking around on / browsing my Site, every once in a while a Pages / Posts content does not finish loading, and i get the below error in my apache log.

[Wed Feb 28 14:29:36 2007] [error] PHP Warning: preg_replace() [<a href='function.preg-replace'>function.preg-replace</a>]: Compilation failed: lookbehind assertion is not fixed length at offset 10 in /wp-includes/formatting.php on line 76

Does anyone else have this Issue?

Thanks a lot,
Overrider

Change History (6)

comment:1 @netmaniac8 years ago

I have this issue also - FBSD 6.1, Apache 2.1.9_6, PHP-5.2.1_3, Wordpress 2.1.1

comment:2 @abtime8 years ago

I also have this problem on FreeBSD6.2 amd64 and i386, Apache 2.2.4 with php5.2.1_3, it did not show up with php5.2.1_2 or php5.2.1_1.

comment:3 @foolswisdom8 years ago

  • Milestone changed from 2.1.3 to 2.2

comment:4 @abtime8 years ago

  • Resolution set to fixed
  • Status changed from new to closed

This has been resolved as bogus, in my opinion.
It turned out the php5-pcre port on FreeBSD had some library compatibility problems (whatsoever), which would turn up in rare circumstances when using pcre with utf-8 strings, escpecially with lookbehind or readahead assertions.
My workaround was to use nl2br for that part in the pee-function that uses lookbehind for inserting <br />s. But after all, recompiling a newer fixed port version of php5-pcre made the problems go away.

comment:5 @foolswisdom8 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:6 @foolswisdom8 years ago

  • Milestone 2.2 deleted
  • Resolution set to invalid
  • Status changed from reopened to closed

abtime, thanks for following up with us!

Note: See TracTickets for help on using tickets.