4.8.2 update today error

Hi,

Sorry to hear you are having problems.

One reason for error 500 is that your web server may be misconfigured. If you are sure that your web server is configured properly, this error can be caused by PHP encountering a fatal error, but not being able to display that error due to error reporting settings. If you wish to display the error text, please make sure that both WP_DEBUG and WP_DEBUG_DISPLAY are set to true.

It looks like a problem related to the feed to post add-on.

PHP Fatal error: Call to undefined function wprss_autoloader() in /home/username/public_html/blopp/wp-content/plugins/wp-rss-feed-to-post/wp-rss-feed-to-post.php on line 109

I went in via cPanel and renamed the feed to post add-on. Then I could access my site again.
Had to re activate the RSS aggregator plugin and then the update went well. After that I reactivated the feed to post add-on.

And my site is now back on track it seems.

In the future, is it a good idea to deactivate the add-ons first before upgrading the main plugin?

I also ran into the error when installing the plugin update.

Fatal error: Call to undefined function wprss_autoloader() in /home/vpn365/public_html/wp/wp-content/plugins/wp-rss-categories/wp-rss-categories.php on line 64

Fatal error: Call to undefined function wprss_autoloader() in /home/vpn365/public_html/wp/wp-content/plugins/wp-rss-excerpts-thumbnails/wp-rss-excerpts-thumbnails.php on line 83

Both these errors take the site down and will not allow access to the WP Control Panel. The only way I was able to get back online was to rename the plugin directories via FTP so the plugin add-ons were disabled. Then after the core was updated, rename and reactivate the add-ons.

The issue seems to occur if you have any of your paid add-ons. This is way beyond a non-technical user – you should pull this update until you get this straightened.

Hi,

The error you received indicates that at that particular moment in time the Feed to Post add-on was active, but the core WP RSS Aggregator plugin was not. The core plugin must always be active when add-ons are active. Under normal circumstances, it should be impossible for an administrator to activate one of our add-ons without having the core plugin active; however, it is possible that this happens as a result of some error internal to WordPress, such as if the core plugin fails to update for some reason. So, to answer your question, it should not be necessary to de-activate add-ons to update the core plugin; however, in your case it may be necessary, if you continue receiving such errors.

We will look further into this, and if we find a problem that we can fix, the fix will be included into one of the future releases. Thank you for reporting this. If you continue having this problem, or other problems related to add-ons, please get in touch with us via the Premium support service.

This happened a while ago for me too, and has done it again with this update. See this post, as you guys are aware of it: https://www.ads-software.com/support/topic/cant-activate-plugin-47?replies=9

Hi dooza, thanks for letting us know. As Anton mentioned, we’re looking into this to see what might cause it to happen, and will fix accordingly if needed.