If you have troubles since the update to WordPress 4.5 please read this post before opening a new thread.
June 29, 2011 at 2:13 am #4826
I just installed the theme and am encountering an error message that is displayed at the top of the page when I view the site.
Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (?< at offset 3 in /nfs/c02/h12/mnt/29739/domains/newsite.sweetstuffstudios.com/html/wp-content/themes/velvet/framework/php/function-set-avia-frontend.php on line 777
class=”page page-id-7 page-template page-template-default logged-in boxed Firefox Firefox?”>
Thanks for your help!
-SharonJune 29, 2011 at 11:09 am #47639June 29, 2011 at 3:55 pm #47640July 5, 2011 at 5:04 pm #47641
I’m experiencing the same problem. Running PHP 5.2.14. Tried with WordPress 3.2, 3.1.4 and 3.1.3 and the error occurs on all versions. Thanks in advance for your assistance.July 6, 2011 at 9:12 pm #47642
Just wondering if there was any update on this or if you are looking into it.
Thanks for your help!July 7, 2011 at 12:42 am #47643
All we can do is check if you’re running the most recent releases. The problem shouldn’t occur when you freshly install the theme. Are you running any plugins or have you modified anything?July 11, 2011 at 11:17 pm #47644
Ok, just tested this on a fresh installation of WordPress 3.2, absolutely no plugins or any modifications of any kind. I haven’t even made any posts other than “Hello world”. The server is running PHP 5.2.14.
I am still getting the preg_match_all() error in both Firefox and Safari (Mac).
I don’t see this error when viewing your demo site…
Thanks for any help or suggestions you might have.July 11, 2011 at 11:19 pm #47645
The error says
unrecognized character after (?< at offset 3 in function-set-avia-frontend.php on line 777July 12, 2011 at 6:38 am #47646
We’re also having the same issue. We’re running everything off a fresh installation, latest version of WordPress 3.2, PHP5+, no modifications whatsoever or plugins installed… and we still get the exact same error.
Looking forward to getting your support on this issue, thanks.July 13, 2011 at 7:24 am #47647
I’ll report it to Kriesi – maybe it’s a bug or the errors occur with a certain configuration only….July 14, 2011 at 9:41 pm #47648
Any updates on this issue? We essentially can’t move forward on building a site with this template without a fix first.July 15, 2011 at 9:27 am #47649
Hey guys! I wasn’t able to reproduce the bug, could any of you send me login data to your wordpress backend, as well as to your FTP account so I can take a look at it myself?
Please also include a link to this thread so I know what the mail is about :)
KriesiJuly 22, 2011 at 6:22 pm #47650
The topic ‘preg_match_all error’ is closed to new replies.