Title: Critical Parse Error, unexpected ‘)’ Last modified: June 19, 2023 --- # Critical Parse Error, unexpected ‘)’ * [oldretiredguy](https://wordpress.org/support/users/oldretiredguy/) * (@oldretiredguy) * [2 years, 11 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/) * About 3 days ago, I received a white screen of death, and Host Gator told me that I had an issue with Crio. The first tech I talked to was able to revert to an older version of PHP, which worked for about an hour. He told me I needed to work directly with BoldGrid. The second tech told me there was an unexpected error in line 270, which was a closing parentheses “)” * **Parse error**: syntax error, unexpected ‘)’ in **/home4/kuhnates/public_html/ wp-content/themes/crio/inc/boldgrid-theme-framework/includes/class-boldgrid-framework- comments.php** on line **270** * ![](https://wordpress.org/56cef40b-e1e5-49ec-9cbf-19531a742129) * ![](https://wordpress.org/029ec07a-504a-4e84-8408-d2776fd6360d) * WordPress version 6.2.2 * Active theme: Crio (version 2.20.3) * Current plugin:  (version ) * PHP version 7.0.33 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcritical-parse-error-unexpected%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 5 replies - 1 through 5 (of 5 total) * [brandonco](https://wordpress.org/support/users/brandonco/) * (@brandonco) * [2 years, 11 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/#post-16836880) * Hi [@oldretiredguy](https://wordpress.org/support/users/oldretiredguy/), * Thank you for reaching out although I’m sorry to hear you’re having trouble with your backups. Just reviewing your specs I see that you’re on PHP version 7.0.33, that is correct this is a long deprecated version of PHP. I think the recommendation now is to upgrade to at least PHP version 8.0. * We would like to review your full backup log to see if it might reveal anything further. To send us your backup log navigate to **Total Upkeep > Tools > Logs** and look for your most recent log. It will have a name like archive-XXXXXXXX. log. * You can use copy the log into [https://codeshare.io/](https://codeshare.io/) and create a link to paste it here in the thread. We should be able to use your backup log to get some more information about what went wrong. * Thanks [@oldretiredguy](https://wordpress.org/support/users/oldretiredguy/), we look forward to assisting you further with this! * Thread Starter [oldretiredguy](https://wordpress.org/support/users/oldretiredguy/) * (@oldretiredguy) * [2 years, 11 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/#post-16838605) * You’ve asked me to “navigate to **Total Upkeep > Tools > Logs** “. Where do I find that? I searched through the control panel, dashboard, about an hours worth of Google searches. Please be more specific on where the log is located, * [brandonco](https://wordpress.org/support/users/brandonco/) * (@brandonco) * [2 years, 11 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/#post-16840008) * I apologize [@oldretiredguy](https://wordpress.org/support/users/oldretiredguy/), You can disregard the bit about Total Upkeep. Based on the error type I assumed this was a backups and migrations error with Crio. * What we actually need to confirm here is the exact PHP version from the **Tools > Site Health > Status > Server** section of your WordPress Dashboard and look for the PHP version displayed there. If you’re running PHP version 7.0.33 I think deprecated code is the issue. * You will either need to manually update your code and remove the syntax error or upgrade to at least PHP 8.0 to bring the code to compliance. * My apologies for the confusion but we do look forward to hearing back from you [@oldretiredguy](https://wordpress.org/support/users/oldretiredguy/)! * Thread Starter [oldretiredguy](https://wordpress.org/support/users/oldretiredguy/) * (@oldretiredguy) * [2 years, 10 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/#post-16897603) * My site is still down, even though the PHP was updated to PHP 8.2 (ea-pp82) * [brandonco](https://wordpress.org/support/users/brandonco/) * (@brandonco) * [2 years, 10 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/#post-16900438) * Hi [@oldretiredguy](https://wordpress.org/support/users/oldretiredguy/), * I’m sorry to hear you’re still having issues. Most web host recommend PHP 8.0 as the most stable version of PHP to run and I believe WordPress themselves still recommend PHP 7.4. I think PHP 8.2 is actually still in beta for testing purposes so maybe try scaling your PHP version back to 8.0. * You reach out to the BoldGrid support team directly if you would like and we can take a deeper dive into this issues in [our support forum](https://www.boldgrid.com/support/ask-a-question/). * Thanks [@oldretiredguy](https://wordpress.org/support/users/oldretiredguy/)! I hope we can get this resolved soon. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Critical Parse Error, unexpected ‘)’’ is closed to new replies. * ![](https://i0.wp.com/themes.svn.wordpress.org/crio/2.22.13/screenshot.jpg) * Crio * [Support Threads](https://wordpress.org/support/theme/crio/) * [Active Topics](https://wordpress.org/support/theme/crio/active/) * [Unresolved Topics](https://wordpress.org/support/theme/crio/unresolved/) * [Reviews](https://wordpress.org/support/theme/crio/reviews/) * 5 replies * 2 participants * Last reply from: [brandonco](https://wordpress.org/support/users/brandonco/) * Last activity: [2 years, 10 months ago](https://wordpress.org/support/topic/critical-parse-error-unexpected/#post-16900438) * Status: not resolved