Title: Parse Error after latest update
Last modified: April 20, 2021

---

# Parse Error after latest update

 *  Resolved [akirastudio](https://wordpress.org/support/users/akirastudio/)
 * (@akirastudio)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/parse-error-after-latest-update/)
 * Your latest update is broken, we get Parse error: syntax error, unexpected ‘const’(
   T_CONST), expecting variable (T_VARIABLE) in /home/customer/www/privit.com/public_html/
   wp-content/plugins/so-widgets-bundle/base/inc/lib/Less/Version.php on line 11
   
   There has been a critical error on this website. after updating, have also trued
   to re-install.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [Andrew Misplon](https://wordpress.org/support/users/misplon/)
 * (@misplon)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/parse-error-after-latest-update/#post-14343340)
 * Hi, thanks, we’re investigating. We aren’t sure of the cause yet. We haven’t 
   been able to replicate the issue on our testing servers.
 * If possible, please, could you let us know the PHP version being used on the 
   server. If you aren’t sure, [https://wordpress.org/plugins/server-ip-memory-usage/](https://wordpress.org/plugins/server-ip-memory-usage/)
   is a quick way to find out.
 * [https://wordpress.org/plugins/wp-rollback/](https://wordpress.org/plugins/wp-rollback/)
   is an easy method of rolling back the Widgets Bundle. Alternatively, you can 
   download the previous version at [https://wordpress.org/plugins/so-widgets-bundle/advanced/](https://wordpress.org/plugins/so-widgets-bundle/advanced/),
   scroll down to Advanced Options.
 *  Thread Starter [akirastudio](https://wordpress.org/support/users/akirastudio/)
 * (@akirastudio)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/parse-error-after-latest-update/#post-14343344)
 * We fixed this our end, we were on PHP 7.0 now 7.3 and all works fine, hope this
   helps.
    -  This reply was modified 5 years, 1 month ago by [akirastudio](https://wordpress.org/support/users/akirastudio/).
 *  Plugin Support [Andrew Misplon](https://wordpress.org/support/users/misplon/)
 * (@misplon)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/parse-error-after-latest-update/#post-14343359)
 * Super, thanks for the update. We’re glad to hear you’ve made progress. Sorry 
   for the hassle.
 *  Plugin Support [Andrew Misplon](https://wordpress.org/support/users/misplon/)
 * (@misplon)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/parse-error-after-latest-update/#post-14343387)
 * A quick technical explanation for anyone reading and wanting to know more. The
   Less update included in the Widgets Bundle specifies the visibility of class 
   constants [here](https://github.com/siteorigin/so-widgets-bundle/blob/develop/base/inc/lib/Less/Version.php#L11-L13).
   The ability to specify the visibility of class constants was only added in PHP
   7.1 ([ref](https://stackoverflow.com/questions/51567998/parse-error-syntax-error-unexpected-const-t-const-expecting-variable-t-v/51568547)).
   We’ll release an update shortly to ensure compatibility below PHP 7.1. Apologies
   again for the hassle.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Parse Error after latest update’ is closed to new replies.

 * ![](https://ps.w.org/so-widgets-bundle/assets/icon.svg?rev=2556862)
 * [SiteOrigin Widgets Bundle](https://wordpress.org/plugins/so-widgets-bundle/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/so-widgets-bundle/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/so-widgets-bundle/)
 * [Active Topics](https://wordpress.org/support/plugin/so-widgets-bundle/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/so-widgets-bundle/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/so-widgets-bundle/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Andrew Misplon](https://wordpress.org/support/users/misplon/)
 * Last activity: [5 years, 1 month ago](https://wordpress.org/support/topic/parse-error-after-latest-update/#post-14343387)
 * Status: resolved