• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

PHP Parse error: syntax error, unexpected '?' in /usr/share/plesk-wp-cli/php/wp-cli.php(23)

Pa1

New Pleskian
Hello all,

i have installed Plesk 12, and total 14 Wordpress Installations running.

I have set up 2 of them using the Plesk Auto Install tool and they appear fine in the admin control Panel. After doing that, i wanted to add the other 12, and did a scan in the tab "wordpress installations"

6 of my Installation was added as expected. the other 6 failed, and i see only entries "httpdocs" in the list.
when clickin on those, it shows the errors:

PHP Parse error: syntax error, unexpected '?' in /usr/share/plesk-wp-cli/php/wp-cli.php(23)

obviously it produces an error when parsing the wp-config files, so i compared the wp-config of a working Installation with one of those that did not work. But they are (apart of username and Passwort) exactly the same Content (used the tool winmerge to be absolute sure)

does anyone have an idea how i can add the other 6 installations manually, or how i can work around that error ?
 
Can you send me two config files (one that works and one that doesn't) via PM? You should remove the passwords, obviously.
 
Last edited:
Thanks to CUSTER. He worked out the solution.

Installing Notepad ++, opening the wp-config.php and then save it as UTF8 without BOM resolved the Problem.

Thanks for the great Support !
 
Back
Top