Serious problem with TinyMCE on join form

I am having a serious issue with the TinyMCE (HTMLtextArea) field on my join form (RC2).   When it gets to the page with that field, it will just "hang" when you click the "join now" button - i.e. nothing will happen.  If you remove the content from this field, the join will proceed normally.   This happened earlier with the "DescriptionMe" field, so I removed it and made a custom TinyMCE field - which seemed to work for a while but no longer does.   I tested this on two browsers to eliminate cache as a possibility.  Again, if that field is cleared (I don't have it set for required) I can get the join form to work properly.   Is anyone else having this issue?   The join form is obviously the most critical component of the system, so for this not to work is a "show stopper".  Does anyone have any idea of what might be wrong, and how I can fix it.

Thanks

Rob

I have been having a hell of a time just trying to get my join form working through all these betas and RCs - the most critical part of the system.

I desperately need to have a working join form.  Could someone advise me - if I change the data type on this form back to a plain text area field, from a htmlTextArea (TinyMCE) field will I lose any data?   In other words, I open up the field definition block in profile fields builder and change it from HtmlTextArea to plain old TextArea will my data still be there?

I still want to get this fixed obviously - I was the one who pushed for TinyMCE in the DescriptionMe field - but I must get operational again.

Rob

No one else having this issue?  Everything worked fine with RC1 but this stopped working with RC2.  I kinda wish they had given us a few days to see what having a working site was like before breaking it with another upgrade.   Not having a working join form has made my site useless.   I might replace the HtmlTextArea with a plain test area field, but I would like to have this function work - I was one of the people who pushed for it.    I just tested editing the HtmlTextArea field in the profile while logged on and got the same issue - it just hangs.   On my second attempt though, it exploded in errors (pasted below) which may give a clue.    Any techies out there who might be able to help interpret this, and possibly give me some idea on how to fix.   Any help would be appreciated.

Rob

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

Warning: Cannot modify header information - headers already sent by (output started at /var/www/vhosts/calstartup.com/httpdocs/plugins/phpids/IDS/Monitor.php:445) in /var/www/vhosts/mysite.com/httpdocs/inc/design.inc.php on line 133

Hey Rob, this is obviously an issue with the phpIDS filter. I cannot access my site from work because they block "social networking" sites. If someone else does not answer this by the time I get home (approx. 3hrs.) then I will try and duplicate this issue with my site and see if we can resolve it.

Chris

Thanks so much for your response Chris.  I hate to sound like an idiot, but what exactly is this phpIDS filter?  By any chance is that a part of a mod I could uninstall?

Rob

Im afraid not Rob. Its a new security feature integrated in Dolphin that prevents (sometimes too much) the "possible attacks" on your website.

All of these Possible Attacks come from this feature detecting SQL Injections, harmful HTML codes, etc.

Chris

Hey rob ...this is 3rd party and can be read up on.

i opened monitor.php and found...interesting stuff

/**
* PHPIDS
*
* Requirements: PHP5, SimpleXML
*
* Copyright (c) 2008 PHPIDS group (http://php-ids.org)
*
* PHPIDS is free software; you can redistribute it and/or modify
* it under the terms of the GNU Lesser General Public License as published by
* the Free Software Foundation, version 3 of the License, or
* (at your option) any later version.
*
* PHPIDS is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public License
* along with PHPIDS. If not, see <http://www.gnu.org/licenses/>.
*
* PHP version 5.1.6+
*
* @category Security
* @package  PHPIDS
* @author   Mario Heiderich <mario.heiderich@gmail.com>
* @author   Christian Matthies <ch0012@gmail.com>
* @author   Lars Strojny <lars@strojny.net>
* @license  http://www.gnu.org/licenses/lgpl.html LGPL
* @link     http://php-ids.org/
*/

/**
* Monitoring engine
*
* This class represents the core of the frameworks attack detection mechanism
* and provides functions to scan incoming data for malicious appearing script
* fragments.
*
* @category  Security
* @package   PHPIDS
* @author    Christian Matthies <ch0012@gmail.com>
* @author    Mario Heiderich <mario.heiderich@gmail.com>
* @author    Lars Strojny <lars@strojny.net>
* @copyright 2007 The PHPIDS Group
* @license   http://www.gnu.org/licenses/lgpl.html LGPL
* @version   Release: $Id:Monitor.php 949 2008-06-28 01:26:03Z christ1an $
* @link      http://php-ids.org/
*/

@Zarcon - oh, that thing - that makes it so secure it seems to block us and our members from using the system.   I appreciate your offer but I doubt you can duplicate it - I imagine almost everyone uses the "DescriptionMe" or a HtmlTextArea field somewhere on their join form.

@Mrpowless - thanks for the info.  Good to see you are jumping in on the RC - we need your insights here.

I've put in a technical support request to Boonex on this.  Hopefully I can get them to take a look, especially since I had this working fine on RC1 before I upgraded to RC2.

Rob

The PHP PCRE extension has been compiled without support for unicode characters (international characters) on your server. Compile the extension with unicode support (--enable-unicode-properties) or ask your provider to do it.

Where would you find this on the server settings??  I am havign the same issue after upgrading to RC2???

Dolphin Admin Panel > Tools > Hosting Tools > Phpinfo (tab) 

For comparison Im running PHP 5.2.11 and PCRE version 7.9 2009-04-11. I do not have this problem. This will be an issue if you are not running PHP 5.1.6+

I recall reading houstonlively mentioned the sudden jump to PHP5 as a requirement in RC2, this may be related. I never ran RC1

@ Sydeburnz -  wow - thank you.  I've had no luck at getting Boonex to address this or even acknowledge it.   I'll check with my host and see if they can help.  How did you figure this out?

@badike -  thanks for posting.  It is good to know I am not all alone in the world.  I wasn't ready for an upgrade anyway, and was delighted that I FINALLY had a working system, and it is completely demoralizing to have the upgrade break it - especially for the most critical component.

Rob

I'm updating my php now....

I have:

PCRE Library Version 7.2 2007-06-19

and the tinymce works fine.

I never really liked tinymce and will swap all out with fckeditor

You can join good here:

http://darrenpowless.com/7rc2

They don't call me the Memphis heart breaker and computer whisperer for nothing :) 

Houstonlively made a post about php 5.2 being a new unforeseen requirement and that put me on the scent. Mrpowless posted the offended file that clearly stated 5.1.6+ as a requirement. The actual error message in google provided the rest. 

This is only PHP and MySql rearranged in a different way. There is no error or issue that hasn't been seen before by someone running something else. Google is a troubleshooters best friend when it comes to error messages as error messages are set in stone by the creator.

Mike

Thanks Sydeburnz I asked support at my server Arrixe to enable unicode and quoted them your solution.

Below is what they did and I just went to admin profile and put !! in the tinymce and no more problems with error warning or it not saving or being spammed with possible security attack emails.... I gave you a point for your wonderful answer and am very greatfull .

Thank you so much.

Jennifer

I have enabled unicode support for PHP-PCRE.

root@panther [~]# pcretest -C | grep Unicode
  Unicode properties support

FYI - this has apparently been fixed in RC3.  My hosting company plans the PCRE / Unicode upgrade this weekend, but they haven't done it yet, however my join form started working again with this upgrade.