Good question … I'd like to know as well. Thanks, guys.   :cool:

This one is new to me. It seems that the PCRE (Pearl Compatible Regular Expression) extension is simply not working since the server upgrade. Although it's called an extension, PCRE is provided by default so it should be possible to rely on it.

I've been googling too and I don't think it's associated with a particular version of php. The common factor seems to be that it happens when php has been compiled with an out of date or incompatible version of PCRE. It's also possible that UTF-8 support is missing and contributing to the problem. This is one of the more authoritative pages I found on Google – http://stackoverflow.com/questions/2106 … port-utf-8

So it doesn't look like something you can fix yourself.

I could show you how to bypass the one line that's throwing an error but svManager uses PCRE in maybe 30 different lines of code, so that will probably just move the problem on and it might be worse next time.

Try leaning on your server support again and please let us know the outcome.

jack

reply from tech team

====
Thank you for your co operation so far. We appreciate your patience as well.

While we investigate this, we could see it is an exception/runtime error thrown as the return value of the function  'preg_match_all()' .

If we can go little extended from our scope of support the regular syntax of the function is as follows,

int preg_match_all ( string $pattern , string $subject , array &$matches [, int $flags ] [, int $offset ] )

The inappropriate input values for this function parameters could also be an issue while executing.  And this is obvious PHP code and doesn't relate much with the hosting functions. 

However, technically the PHP version compatibility could also be a part of the problem. We shall place the right version of the PHP on the server as recommended by your development team.

So we would require you to confirm with us the precised PHP version you would like to deploy on the server for this function be executed successfully.

Once confirmed, we shall try with the recommended version of PHP and check if that helps. So please review the the PHP script with the development team and please get back for further assistance.

Please share with us your additional queries.

Your server's current PHP version is 5.2.17 and the available versions are,

5.2.9
5.3.15
5.3.16
5.4.6

===

Jack, what should me next response be?
thanks

Very interesting.

If you look to the end of the output, you'll see that the error is still there, so the PCRE function on its own outside svManager is still blowing-up. That's good news – diagnosis is a lot simpler if we can reproduce the problem with one line of code.

The phpinfo output is interesting as well:
It seems you are running php v5.3.15
The PCRE version is version 6.6 dated 06-Feb-2006

Take a look at this post – the guy fixed a similar problem to yours by upgrading PCRE on the server to the current v8.10.

Before you go back to your server people, there is one more thing we could try. Could you change one line in the test script as follows:

var_dump(preg_match_all('(.*\.((jpe?g)|(png)|(gif))$)i', 'test.jpg', $matches));

It's almost the same as the previous version except that I've deleted a single lower case u. The u stands for utf-8 character support. I don't see any utf-8 support in the output from phpinfo so that could be contributing to the problem.

jack

Ah – we no longer get the error.

I think you can remove the lower case letter u from svManager. Since your server doesn't seem to support unicode anyway then you probably won't lose anything. I've checked through the code and I think the other calls to PCRE won't cause a problem. I think it's just the one line of code but we can't be 100% sure till we try it.

So take a backup.

Edit the file svmanager/classes/gallery.php

Line 687 should look like this:

return (0 != preg_match_all('(.*\.((jpe?g)|(png)|(gif))$)ui', $fileName, $matches));

If you have any problem finding it then search for function isImage
Delete the u so the line reads:

return (0 != preg_match_all('(.*\.((jpe?g)|(png)|(gif))$)i', $fileName, $matches));

It remains a mystery why it used to work on your server and now it doesn't. I still think there is a problem with the server setup since the upgrade but if we can get it working with svManager then we don't need to worry about that.

jack