Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Installing SilverStripe /

Getting SilverStripe up and running on your computer and on your web server.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Compilation failed, ShortcodeParser.php?!?!


Go to End


5 Posts   3613 Views

Avatar
Pix

Community Member, 158 Posts

2 April 2013 at 2:08pm

Edited: 02/04/2013 2:08pm

With SilverStripe-cms-v3.1.0-beta2 I get:

[Warning] preg_match_all(): Compilation failed: unrecognized character after (?< at offset 20
GET /rs3/SilverStripe-cms-v3.1.0-beta2/
Line 207 in /home/testsite/public_html/rs3/SilverStripe-cms-v3.1.0-beta2/framework/parsers/ShortcodeParser.php

Server is running Centos 5.8, PHP 5.3.3

The install seems to go, but that's what i get when trying to go to the site. What the heck and how to fix?!?!

Thanks

Avatar
Invader_Zim

Community Member, 141 Posts

3 April 2013 at 2:36am

Hi,
I never had this error, but it could be a CentOS issue with an outdated pcre package.

Maybe these links are helpful:
http://fooninja.net/2010/10/09/php-warning-unrecognized-character/
http://ankurgupta.com/blog/php-warning-preg_match_all-compilation-failed-unrecognized-character-after-at-offset/

Avatar
Pix

Community Member, 158 Posts

3 April 2013 at 6:11am

Wow that did it, all fixed!!!! Thank you so much, I really appreciate it!!!

:0)

Avatar
neilcreagh

Community Member, 136 Posts

23 September 2013 at 10:45pm

I had this error when upgrading to 3.1 but fixed it just by removing Director::set_environment_type("dev"); from my main _config file

Avatar
Fuzz10

Community Member, 791 Posts

24 September 2013 at 2:00am

@Neil, by doing so, you are probably just suppressing the error messages.

try testing the CMS (TinyMCE).