Title: Fatal Error Last modified: August 21, 2016 --- # Fatal Error * Resolved [steveraven](https://wordpress.org/support/users/steveraven/) * (@steveraven) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/) * Hi, * Up until a week or so ago, this plugin worked fine. Then following an update, my site crashed and I had to uninstall the plugin via my host. * Just tried to upload it again to see if it had been fixed, and it’s installing but will not activate, as there is a fatal error. * Any chance of a fix, so I can ween people off IE? * [https://wordpress.org/plugins/advanced-browser-check/](https://wordpress.org/plugins/advanced-browser-check/) Viewing 8 replies - 1 through 8 (of 8 total) * Thread Starter [steveraven](https://wordpress.org/support/users/steveraven/) * (@steveraven) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973749) * Hang on – just found that my GoDaddy account is running php 5.2 – now upgrading to 5.3. * I’ll let you know in an hour. * Thread Starter [steveraven](https://wordpress.org/support/users/steveraven/) * (@steveraven) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973755) * No, it’s not having it. * The activation is being allowed now, but the website crashes to a white screen of death with the message: * Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home/content/03/7008403/html/mysiteaddress/wp-content/plugins/advanced- browser-check/abc-core.php on line 5 * And on one occasion when I did get a different response, the screen faded to black with the following message: * Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 361 bytes) in /home/content/03/7008403/html/mysiteaddress/wp-content/plugins/ advanced-browser-check/browscap/browscap.php on line 712 * ..after which, the white screen came back on a refresh. * A fix would be nice! * Plugin Author [Mattias](https://wordpress.org/support/users/darkwhispering/) * (@darkwhispering) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973817) * Hi [@steveraven](https://wordpress.org/support/users/steveraven/) * Sorry to hear you have problems. * However, please take a look in the [FAQ](http://wordpress.org/plugins/advanced-browser-check/faq/) for your latest issue. A solution is listed there and there is also other support threads about this as well. [Here is one](http://wordpress.org/support/topic/update-not-working-7?replies=4) specific for GoDaddy * Thread Starter [steveraven](https://wordpress.org/support/users/steveraven/) * (@steveraven) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973823) * Sorry no, it’s not really an acceptable solution to have to go into your hosting panel and increase settings that aren’t supposed to be increased, just to get one plugin to work. * I’ll look elsewhere until you decide to make it work as before. * Thanks anyway! * [Marco Córdoba](https://wordpress.org/support/users/mcordoba/) * (@mcordoba) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973870) * Hi [@steveraven](https://wordpress.org/support/users/steveraven/)! * I had the same issue days some days ago in one of my webs hosted in goDaddy, so I went to cPanel and selected PHP version, changed memory_limit to 256M and voila, everything worked fine! * I believe every plugin has its requirements, you won’t be running Windows 8 in a 486 PC. * You have the solution, It should be marked as [resolved]. * Good job Mattias! * Plugin Author [Mattias](https://wordpress.org/support/users/darkwhispering/) * (@darkwhispering) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973872) * [@steveraven](https://wordpress.org/support/users/steveraven/) I’m sorry, but there will not be a change to the plugin. * Like stated in the FAQ section, the first time the plugin runs it need to create the browscap.ini and the cache.php files and this is a heavy task. * Saying that changing the memory limit is something your not supposed to do is like, imo, saying you should not upgrade your RAM memory in your computer when needed. * Thread Starter [steveraven](https://wordpress.org/support/users/steveraven/) * (@steveraven) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973881) * Changing the memory limit is fine, but exceeding the memory limit (64MB on GoDaddy) is potentially suicide if they catch on, and I will not risk it. * I’m now using [Browser Rejector](http://wordpress.org/plugins/browser-rejector/) which does exactly the same thing, without having to fart about, so marked as resolved, but certainly not by way of the Advanced Browser Check connections! * [maziarom](https://wordpress.org/support/users/maziarom/) * (@maziarom) * [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973893) * Hi Mattias, * I really like your plugin and have been using it for a year now on a client’s site, but they use Siteground shared hosting, and they don’t allow changing the memory limit to higher than 128M. Do you have any ideas for me? * Thanks, Maz Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘Fatal Error’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/advanced-browser-check_ffffff.svg) * [Advanced Browser Check](https://wordpress.org/plugins/advanced-browser-check/) * [Frequently Asked Questions](https://wordpress.org/plugins/advanced-browser-check/#faq) * [Support Threads](https://wordpress.org/support/plugin/advanced-browser-check/) * [Active Topics](https://wordpress.org/support/plugin/advanced-browser-check/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-browser-check/unresolved/) * [Reviews](https://wordpress.org/support/plugin/advanced-browser-check/reviews/) * 8 replies * 4 participants * Last reply from: [maziarom](https://wordpress.org/support/users/maziarom/) * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-1218/#post-4973893) * Status: resolved