Email errors - what now!

I just tried to send an private message to one of my members on a new site, and it exploded in errors - probably because I made the mistake of putting a link in the message:

Warning: preg_replace() [function.preg-replace]: Compilation failed: support for \P, \p, and \X has not been compiled at offset 1 in /var/www/vhosts/mysite.com/httpdocs/plugins/phpids/IDS/Monitor.php on line 445

Warning: preg_replace() [function.preg-replace]: Compilation failed: support for \P, \p, and \X has not been compiled at offset 1 in /var/www/vhosts/mysite.com/httpdocs/plugins/phpids/IDS/Monitor.php on line 446

Warning: preg_replace() [function.preg-replace]: Compilation failed: support for \P, \p, and \X has not been compiled at offset 1 in /var/www/vhosts/mysite.com/httpdocs/plugins/phpids/IDS/Monitor.php on line 445

Warning: preg_replace() [function.preg-replace]: Compilation failed: support for \P, \p, and \X has not been compiled at offset 1 in /var/www/vhosts/mysite.com/httpdocs/plugins/phpids/IDS/Monitor.php on line 446

I don't even know if it was sent, but even if it was, the format appears to be a mess.   It put a "n" character between each line and looks like crap.

Hi John,

Thanks for joining this new site. etc, etc, etc

I went to your website and think you have an interesting company.etc, etc, etc

n

Sincerely

n

Rob

The letter was bragging to a fairly influential person how great the technology is, but obviously all I did was embarrass myself and refuted my own point.  Any thoughts on this one or if there is a fix?

Rob

UPDATE:  Just sent another message - this time without a link, and got the exact same errors, so that had nothing to do with it.

You have to upgrade your version of PHP to 5.1.6+ and/or have PCRE compiled with unicode support. With all your errors you may be better off finding a ISP that better supports Dolphin 7 RC2 + out of the box.

Dolphin 7 requires that your PHP version should be at least 5.2.0, so why would you upgrade your version starting at 5.1.6?

Also, it was mentioned earlier by mauricecano, that for now, you can add a <br> instead of hitting the enter key at the end of your sentence to resolve this issue.

Not sure if this has been reported yet, so we need to get this looked at.

Chris

@Sideburnz.  My host Alterhosting is actually pretty good for a shared service.  They say they will recompile my server with unicode support this weekend.  I appreciate your tracking down that issue - Boonex couldn't figure it out.   If you read some of the experiences people here have with hosting services with the hosts that brag about their Dolphin "support" you might find that things aren't so perfect in their world either.

@Zarcon.  I have php 5.2.8.  Thanks for the tip about the <br> character.

PCRE w/unicode support starts at 5.1.6+. The error he posted directly points to the lack of unicode in PCRE. Sorry for any confusion.

I actually find it quite suprizing that Boonex does not support PHP 5.1.6 at least.

All current distros of Redhat Enterprise and all Enterprise clones such as CentOS come standard with PHP 5.1.6 right up to the current 5.4 distros.

And to make it worse, that stock PHP version does not have PCRE unicode support compiled in.

Thus this basically forces anyone running Redhat Enterprise or CentOS to upgrade their version of PHP the moment the distro is installed if they plan to run dolphin 7.

Kinda sucks if you ask me, but hey, whatever.