jsantari Posted October 17, 2014 Share Posted October 17, 2014 I've just moved a site from my local dev to production server to launch. I've got several 2.4 sites running on this server. Did this in the way I've done it in the past (dump local database, setup new db on production, imported db files, change site/config.php to use new db settings, copy all files from dev to production). When I try to access the site I'm getting this error. Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/turtlefl/public_html/wire/core/Modules.php on line 618 No idea what's wrong here? Saw reference to setting RewriteBase / - tried it but no luck. Never had to on the other sites either. Link to comment Share on other sites More sharing options...
arjen Posted October 17, 2014 Share Posted October 17, 2014 I think your PHP version is not sufficient enough. It need to be > 5.3.8. 5 Link to comment Share on other sites More sharing options...
jsantari Posted October 17, 2014 Author Share Posted October 17, 2014 Yep - after they upgraded the host to 5.4 I had to reset to use 5.2 due to problems with the old Joomla site - set it to use 5.4 and it's working fine. Thanks for the fast response - love pw community help! Link to comment Share on other sites More sharing options...
CliffG Posted November 22, 2014 Share Posted November 22, 2014 You may also need the following at the top of your htaccess file: # Use PHP5.4 as default AddHandler application/x-httpd-php54 .php I had set my site up in a subdirectory for the client to see and it worked fine, but when I moved it to the top level, it threw a 500 server error and the error log showed "unexpected T_PAAMAYIM_NEKUDOTAYIM." So I checked the htaccess file of the WordPress system that I was replacing and there was the magic line that solved the problem. Thank you, jsantari for asking and arjen for your answer. 2 Link to comment Share on other sites More sharing options...
markoj Posted April 26, 2015 Share Posted April 26, 2015 Same exact thing just happened to me, moving a PW site from a working subdirectory to the root where wordpress was before. I didn't get that PAAMAYIM error at first, just a 500 error. I installed a clean version of PW and then got the PAAMAYIM things which googling led me to this post. Switching php versions back and forth through the host cpanel made it create new php.ini files which fixed it. Thanks! Link to comment Share on other sites More sharing options...
Can Posted May 22, 2015 Share Posted May 22, 2015 Have 2 PW installs on the same machine, only different domains/folders One I upgraded from 2.5.29 (or so) so from dev to 2.6 shortly after it was launched Everything worked great, ah this one I updated using SystemUpdate module The second one I just updated from 2.4.0 to 2.6 and got the T_PAAMAYIM_NEKUDOTAYIM error (front- & backend) cleared everything, only switching PHP from 5.2 to 5.3 did it The first one runs perfectly fine on PHP 5.2 Just wanted to share this experience One question, is there any downside having PHP 5.3 but as cgi instead of 5.2 as apache module? Saludos 1 Link to comment Share on other sites More sharing options...
cstevensjr Posted May 22, 2015 Share Posted May 22, 2015 In ProcessWire 2.5 or 2.6 the minimum PHP version is 5.3.8. Running your installation at any version less than what is stated is certainly possible but not supported. FYI, PHP 5.2 End-Of-Life was 6 January 2011. PHP 5.3 End-Of-Life was 14 August 2014. As the official PHP website states If you are using these releases, you are strongly urged to upgrade to a current version, as using older versions may expose you to security vulnerabilities and bugs that have been fixed in more recent versions of PHP. 2 Link to comment Share on other sites More sharing options...
Can Posted May 22, 2015 Share Posted May 22, 2015 Good that I wrote my stuff! Thanks for remembering me on that, just updated to 5.6, luckily everything still worked or at least seems to work.. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now