Title: Fatal error Last modified: August 31, 2016 --- # Fatal error * Resolved [proof_fairy](https://wordpress.org/support/users/proof_fairy/) * (@proof_fairy) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/) * Trying to install this plugin on a friend’s stie and it triggers a fatal error message: * Parse error: syntax error, unexpected T_FUNCTION in /home/sites/max-inheritance. co.uk/public_html/wp-content/plugins/tracking-code-manager/index.php on line 12 * Basically the guy had the plugin installed and then went to update it – but it totally crashed the site, just brought up a white screen both front end and back end. * I am no expert … but I went in via FTP, changed the plugin name to .old, got the site running again and then deleted from within WordPress. Then tried to reinstall plugin to try again and it brings the error message. * Any advice most appreciated! * [https://wordpress.org/plugins/tracking-code-manager/](https://wordpress.org/plugins/tracking-code-manager/) Viewing 8 replies - 1 through 8 (of 8 total) * Plugin Contributor [intellywp](https://wordpress.org/support/users/intellywp/) * (@intellywp) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044729) * Hi Proof, Thanks for choosing IntellyWP products. I suppose that this is something connected to your PHP version due to the line 12 of the index.php is basically a function declaration. * I tried to reproduce your issue with the test websites that we already have but unfortunately we are not able to reproduce your issue. If you like the idea we could connect to your website and fix it. In that case, we only need a valid WP credential that you can fill here [https://intellywp.com/report-a-bug/](https://intellywp.com/report-a-bug/) * Cheers, Simon. * Plugin Contributor [intellywp](https://wordpress.org/support/users/intellywp/) * (@intellywp) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044786) * Hi proof_fairy We close this thread due to we already provided the information to fix this. We hope that you can open the ticket so we will see what cause this issue in your website. Bye, Simon. * [gimmeopenroad](https://wordpress.org/support/users/gimmeopenroad/) * (@gimmeopenroad) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044972) * I’m having the exact same problem. Please let me know if you figure out a fix. Thanks! * Plugin Contributor [intellywp](https://wordpress.org/support/users/intellywp/) * (@intellywp) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044973) * The function that we use (at line 12 of the file index.php) is introduced in PHP 5.3.0 Wordpress requirements suggest using at least PHP 5.6.0 ([https://wordpress.org/about/requirements/](https://wordpress.org/about/requirements/)) Let me know if, as I suppose, you PHP version is older. * [gimmeopenroad](https://wordpress.org/support/users/gimmeopenroad/) * (@gimmeopenroad) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044975) * OK I use Justhost, [https://my.justhost.com/cgi/help/447](https://my.justhost.com/cgi/help/447) Would you recommend I switch to the PHP 5.6 (FastCGI) option out of that list of options? * Thanks again * Plugin Contributor [intellywp](https://wordpress.org/support/users/intellywp/) * (@intellywp) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044976) * Hi Gimme, Typically FastCGI is the better choice but we are not “hosting” expert. * If is possible try to update to PHP 5.6 FastCGI and see if everything works well( not only our plugin but your website in general). If something goes wrong I suppose you can return back to your previous version. * I don’t know which PHP version do you have installed now, but if can try to do this will be a good idea, be aware that currently PHP has released the 7 version so PHP 5.6 is a very good and stable version. * Let us know, Simon. * [gimmeopenroad](https://wordpress.org/support/users/gimmeopenroad/) * (@gimmeopenroad) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044978) * Thanks Simon, I appreciate you’re help. You are PROBABLY right, but after reading a bit more I am personally too scared to change the PHP version of my server since I have about 30 sites running on it and it’s just not worth the risk to me of breaking them in unforeseeable ways. I just installed a different tracking code plugin for a quick fix. Thank you anyway for your help, and best of luck! * Plugin Contributor [intellywp](https://wordpress.org/support/users/intellywp/) * (@intellywp) * [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044980) * Absolutely agree with you! If you have 30 websites you need to pay attention if you need to change this. Some hosting allow also change the PHP version only for a specific website so you can test one website per time if everything works well. If you need our help you are welcome, Simon. Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘Fatal error’ is closed to new replies. * ![](https://ps.w.org/tracking-code-manager/assets/icon-256x256.jpg?rev=2749278) * [Tracking Code Manager](https://wordpress.org/plugins/tracking-code-manager/) * [Frequently Asked Questions](https://wordpress.org/plugins/tracking-code-manager/#faq) * [Support Threads](https://wordpress.org/support/plugin/tracking-code-manager/) * [Active Topics](https://wordpress.org/support/plugin/tracking-code-manager/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/tracking-code-manager/unresolved/) * [Reviews](https://wordpress.org/support/plugin/tracking-code-manager/reviews/) ## Tags * [Crash](https://wordpress.org/support/topic-tag/crash/) * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/) * 8 replies * 3 participants * Last reply from: [intellywp](https://wordpress.org/support/users/intellywp/) * Last activity: [10 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-2002/#post-7044980) * Status: resolved