Title: Fatal Error
Last modified: April 24, 2017

---

# Fatal Error

 *  Resolved [Nick Murray](https://wordpress.org/support/users/nickfmc/)
 * (@nickfmc)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2533/)
 * My site was set to auto update and it went down today after the latest updates,
   I disabled the plugin via FTP to get the site back online but can not reactivate
   the plugin, I tried reverting to an old plugin version 2.0.0 and I get the same
   issue. When trying to activate the plugin I get the following error.
 * Parse error: syntax error, unexpected ‘[‘ in /wp-content/plugins/user-access-
   manager/user-access-manager.php on line 168

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

 *  Plugin Author [gm_alex](https://wordpress.org/support/users/gm_alex/)
 * (@gm_alex)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2533/#post-9063114)
 * Your PHP Version is the problem. Beginning from version 2.0.0 UAM requires at
   least PHP 5.4. You have two options:
 * 1. Download an older verion here [https://wordpress.org/plugins/user-access-manager/advanced/](https://wordpress.org/plugins/user-access-manager/advanced/)
   at the “PREVIOUS VERSIONS” section. Delete the current version under wp-content/
   plugins and upload the older version.
    2. Update your PHP version to a version
   higher or equal PHP 5.4.
 * I would recommend the second option, because the latest version of PHP 5.3 is
   more than four years old and didn’t received any security updates since that,
   which is a huge security issue on your site. Use at least PHP 5.6 which still
   receives security updates and is full compatible to PHP 5.3. I’m sure your hoster
   will assist you.
 *  [wesselej](https://wordpress.org/support/users/wesselej/)
 * (@wesselej)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2533/#post-9063417)
 * Just as a heads up, I am running this plugin on a site I manage which was using
   PHP 5.4.16, and I encountered an Internal Server Error as well. This was the 
   highest version of PHP 5.4.x they had available. Switching to PHP 7.0.18 was 
   also an option (oddly, with nothing in between), and the site now works with 
   the plug-in using PHP 7.
 *  Plugin Author [gm_alex](https://wordpress.org/support/users/gm_alex/)
 * (@gm_alex)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2533/#post-9063432)
 * [@wesselej](https://wordpress.org/support/users/wesselej/) That’s strange.
 *  Thread Starter [Nick Murray](https://wordpress.org/support/users/nickfmc/)
 * (@nickfmc)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2533/#post-9066171)
 * ours was on PHP 5.3 just for your records. thanks for the quick reply and free
   plugin support!

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

The topic ‘Fatal Error’ is closed to new replies.

 * ![](https://ps.w.org/user-access-manager/assets/icon.svg?rev=1563783)
 * [User Access Manager](https://wordpress.org/plugins/user-access-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/user-access-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/user-access-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/user-access-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/user-access-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/user-access-manager/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [Nick Murray](https://wordpress.org/support/users/nickfmc/)
 * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2533/#post-9066171)
 * Status: resolved