I just upgraded the module and started getting the error below when logged in. Does this mean anything to anyone?

warning: preg_replace() [function.preg-replace]: Compilation failed: support for \P, \p, and \X has not been compiled at offset 5 in /home/MYSITE/public_html/sites/all/modules/glossify/glossify.module on line 189.

Comments

rsvelko’s picture

rsvelko commented

your version of php does not support unicode I guess. Which version are your php, apache, mysql?

If you do not need unicode support (meaning your site uses only the latin letters) - I can add a setting in Glossify to use one or the other preg_replace regexp (latin / Unicode ...)

You can downgrade without any problem (no db update hooks or a db table at all here) to the release before the last 2.1 - see the releases page. The last one bugfix was to change the regexp to a unicode aware... See release notes...

coloryan’s picture

coloryan commented

MySQL and PHP are as follows:

MySQL database 5.0.77
PHP 5.2.6

Not sure about Apache.

I was running the previous version without any issues (thanks!). On one site it worked perfectly, on another site I was having issues. I presumed due to HTML, Panels, and maybe some blocks, but never really looked into it. I was hoping the new version would fix the issue.

If you're curious, I can provide a link to both sites.

rsvelko’s picture

rsvelko commented

your php is modern enough - so the only reason that is left is the regexps module (PCRE)... Write
----
<?php
phpinfo();
----
into a new p.php file under your server's docroot and paste here the "pcre" section of it. The PHP regexp module (PCRE - Perl Compatible Reg Expressions) u are using is maybe too old or sth...

Apache version is not important.

The prev. version did not support Unicode link-from nodes (no autolinks appeared there) but after this bug was fixed - people like you that do not have suport for the newest PCRE PHP lib, have problems.

I am going to add a setting in the admin UI for that - with Unicode support = On by default. So you will have to upgrade to the latest 2.2 I am releasing in 5 mins and then change the setting to Off - please report after that.

---- A second approach is to look into upgrading your PCRE lib, but I have no idea currently how man does that.

Once more:
Upgrade to 2.2 after 15 mins and then turn the Unicode support setting OFF in glossify's admin UI.

rsvelko’s picture

rsvelko commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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