Title: Fatal error message Last modified: January 27, 2017 --- # Fatal error message * Resolved [emenster](https://wordpress.org/support/users/emenster/) * (@emenster) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/) * Plugin could not be activated because it triggered a fatal error. Parse error: syntax error, unexpected T_FUNCTION in /home4/urphutur/public_html/devsite/wp- content/plugins/wp-rss-aggregator/wp-rss-aggregator.php on line 131 * I am also running the most current version of PHP with Host Gator. Viewing 11 replies - 1 through 11 (of 11 total) * [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * (@erricgunawan) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8723200) * Hi [@emenster](https://wordpress.org/support/users/emenster/) * Can you please let us know what PHP version you are using at your site? You can ask this information from your host if you’re not aware of it. * Thread Starter [emenster](https://wordpress.org/support/users/emenster/) * (@emenster) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8729235) * php version 5.4 * [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * (@erricgunawan) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8732588) * Hi [@emenster](https://wordpress.org/support/users/emenster/) * Thank you for the information. * May we ask where did you get the PHP version from? Is it coming from your host? * If so, can you please confirm that it is the actual version of PHP you are using currently at your site? * For example simply do: * `` * anywhere on your site and let us know what the output of that is? * If you’re not sure how to do the above, here is a [link](https://whatswp.com/check-php-version-wordpress/) that might help you to get the PHP version. * Or you can just simply use [this plugin](https://wordpress.org/plugins/display-php-version/). * Thread Starter [emenster](https://wordpress.org/support/users/emenster/) * (@emenster) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8732693) * I’m at Host Gator * PHP ver 5.2.17 * [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * (@erricgunawan) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8746905) * Hi [@emenster](https://wordpress.org/support/users/emenster/), * Then there is your problem. WP RSS Aggregator requires PHP 5.3.9 or higher to run as is explained [here](https://wordpress.org/plugins/wp-rss-aggregator/). * Can you please ask your host provider to upgrade your PHP to a more recent version? * [coryinthelou](https://wordpress.org/support/users/coryinthelou/) * (@coryinthelou) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8782701) * Same issue here at Bluehost running PHP 5.6.29. * What’s odd is that I created a new site over HTTP, installed the WP RSS Aggregator plugin, and it worked fine. Then, I activated the free SSL certificate, switched to HTTPS, and then it threw a 500 error. After deleting the plugin and reinstalling, I’m now getting the same error after activating the plugin: * “Parse error: syntax error, unexpected T_FUNCTION in /home1/coryklei/public_html/ bourbonblvd/wp-content/plugins/wp-rss-aggregator/wp-rss-aggregator.php on line 131” * Any ideas what I can try? I’m very interested in purchasing but want to make sure it all works first. 🙂 * [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * (@erricgunawan) * [9 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8788531) * Hi [@coryinthelou](https://wordpress.org/support/users/coryinthelou/) * The problem you have is usually caused by the PHP version that runs under the minimal requirement. * Please try to confirm if your site really got that PHP version (5.6.29) by following [this guide](https://wordpress.org/support/topic/fatal-error-message-170/#post-8732588). * Also, you were saying that you were able to use the Core plugin once. Then, it changed after you activated the SSL etc. * Since the problem most likely related to a change in your server, can you please ask and confirm your host provider regarding this issue? They might have found something that causing this issue. * [coryinthelou](https://wordpress.org/support/users/coryinthelou/) * (@coryinthelou) * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8797093) * Aha! Sigh, it appears that I also have WP 5.2.17. Guess I’ll have to ask them to upgrade! * [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * (@erricgunawan) * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8797441) * Hi [@coryinthelou](https://wordpress.org/support/users/coryinthelou/) * Thank you for confirming your PHP version (we believe when you say ‘WP’ 5.2.17, it’s actually ‘PHP’ 5.2.17 🙂 ) * Yes, please ask your host provider if they’re able to upgrade it for you. * Hopefully, it would resolve your issue. * [coryinthelou](https://wordpress.org/support/users/coryinthelou/) * (@coryinthelou) * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8799126) * Yes, I meant PHP 5.2.17. Haste makes waste, and all that. * Suddenly your plugin is working again after submitting the support request to Bluehost, despite no intervention (so they say) by them. They maintain that the PHP version is actually 5.6.29, despite the version check in the page reporting 5.2.17. Any idea why there would be such a discrepancy? * [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * (@erricgunawan) * [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8801921) * Hi [@coryinthelou](https://wordpress.org/support/users/coryinthelou/), * To be honest, we don’t know for sure how things happen under the hood of your server setup. * The most important thing is you can get the plugin back running again and your host support are always there whenever you need them. * But if you’d like to really know the reason, you can try to ask them again 🙂 * Also, while I have you here if you like our products or the quality of our support, please consider leaving a positive review [here](https://wordpress.org/support/plugin/wp-rss-aggregator/reviews/). * It would be greatly appreciated by the whole team. * Have a great day! Viewing 11 replies - 1 through 11 (of 11 total) The topic ‘Fatal error message’ is closed to new replies. * ![](https://ps.w.org/wp-rss-aggregator/assets/icon-256x256.gif?rev=3157090) * [RSS Aggregator - RSS Import, News Feeds, Feed to Post, and Autoblogging](https://wordpress.org/plugins/wp-rss-aggregator/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-rss-aggregator/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-rss-aggregator/) * [Active Topics](https://wordpress.org/support/plugin/wp-rss-aggregator/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-rss-aggregator/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-rss-aggregator/reviews/) * 11 replies * 3 participants * Last reply from: [Eric Gunawan](https://wordpress.org/support/users/erricgunawan/) * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-message-170/#post-8801921) * Status: resolved