A Prestashop parse error occurs when we install Prestashop 1.7 or above or accessing the admin panel of the store.
As part of our Server Management Services, we assist our customers with several Prestashop queries
Today, let us see the cause and solution to this error.
Prestashop parse error
We can expect this error in two situations.
a) Recently one of our customers went ahead with the creation of a database, with all right. In addition, he unzipped the downloaded file and uploaded index.php, Install_PrestaShop.html, and prestashop.zip.
However, when he opens the page, the installation does not start. Instead, it shows an error stating:
Parse error: syntax error, unexpected ‘[‘, expecting ‘)’ in /home/user/public_html/XX-MY-PATH/index.php on line 40
b) Similarly, we come across this error when we log in to the Prestashop admin panel:
PHP Parse error: syntax error, unexpected ‘finally’ (T_STRING), expecting catch (T_CATCH) in /home/…………………./public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php on line 201
The major cause for this can be the following:
- Missing lock
- Outdated PHP version
How to resolve this error?
We need to ensure that there is no missing parenthesis in the mentioned file.
In addition, we need to update the PHP version for the admin folder. This can be done from the control panel.
For example, in cPanel, we can update PHP as follows:
- Log in to hosting cPanel.
- Locate the MultiPHP Manager tool in the Software section of cPanel.
- Click the checkbox for the domain(s) that we want to adjust.
- Then from the PHP Version drop-down menu, select the PHP version that best suits site code.
- Finally, click the blue Apply button to save the change.
In order to view PHP Version in cPanel, our Support Techs suggest the below steps:
- Log into cPanel.
- Under General Information on the right panel, click Server Information.
- Under the Item column, find PHP Version.
- In the Detail column, note the version number.
In short, a Prestashop parse error occurs when we install Prestashop 1.7 or above or accessing the admin panel of the store. We saw an effective method our Support Techs employ in order to fix this error.