NukeSEO not working with php 7.1.11

Posted: Wed Jan 31, 2018 5:34 pm

Code:

Parse error: syntax error, unexpected 'new' (T_NEW) in includes/nukeSEO/nukeSEOfunctions.php on line 318

Guys I get this error after choosing for php 7.1.11

Code:

if ( !function_exists('seoGetCurrentVersion') )


{


  function seoGetCurrentVersion ($p1, $debug=0) {


    require_once ('includes/xmlrpc/xmlrpc.php');


    $client =& new xmlrpc_client('/version.php', 'nukeseo.com', 80);


    $client->return_type = 'xmlrpcvals';


    $client->setDebug($debug);


    $msg =& new xmlrpcmsg('script.getCurrentVersion');


    $p1 =& new xmlrpcval($p1, 'string');


    $msg->addparam($p1);


    $res =& $client->send($msg, 0, '');


    if ($res->faultcode()) return $res; 


    else return php_xmlrpc_decode($res->value());


  }


}

Code:

line 318: $client =& new xmlrpc_client('/version.php', 'nukeseo.com', 80);

Update: I got the same error with php 7.0.25 but with php 5.6.32 I don't get this parse error.

SOLVED:

Code:

if ( !function_exists('seoGetCurrentVersion') )


{


  function seoGetCurrentVersion ($p1, $debug=0) {


    require_once ('includes/xmlrpc/xmlrpc.php');


    $client = new xmlrpc_client('/version.php', 'nukeseo.com', 80);


    //$client =& new xmlrpc_client('/version.php', 'nukeseo.com', 80);


    $client->return_type = 'xmlrpcvals';


    $client->setDebug($debug);


    $msg = new xmlrpcmsg('script.getCurrentVersion');


    $p1 = new xmlrpcval($p1, 'string');


    $msg->addparam($p1);


    $res =& $client->send($msg, 0, '');


    if ($res->faultcode()) return $res; 


    else return php_xmlrpc_decode($res->value());


  }


}

removing this symbol

Code:

fixed the error but it comes more and more.

7.0.0 Support for the /e modifier has been removed. Use preg_replace_callback() instead. All preg_replace needs to be replace with preg_replace_callback

Site Admin Joined: Aug 22, 2007 Posts: 1772

Yes, there are more issues like that on this way. This is fixed in my upcoming php7-package of RN25x. I would recommend it to stay on 5.6.x as long this package isn't released.

Posted: Sun Feb 11, 2018 1:59 pm

[ Only registered users can see links on this board! Get registered or login! ]