Version 4.9.1 update = PHP Fatal error with Keyword Filtering addon

You can ignore my previous post from the last time you updated your software.

If you make changes and those changes can take down a site, could you maybe mention that in your changelog? Or maybe stop charging until you get your release process sorted out. This could not have come at a worse time. Was counting on you.

Which files were changed and what changed in those files? I need to fix this now.

Fatal error: Call to undefined function wprss_autoloader() in /home/public_html/domain.org/wp-content/plugins/wp-rss-full-text-feeds/wp-rss-full-text.php on line 83

Hi all,

Sorry to hear that you are having trouble using our plugins.

The wprss_autoloader() function returns an instance of the autoloader class, which is responsible for loading classes, and is contained in the core WP RSS Aggregator add-on. The cause of the errors you are seeing is most likely that the core add-on is inactive. Please make sure it is active, and let us know if the symptoms persist.

Please be advised that the latest version of WP RSS Aggregator, 4.9.1, does not contain any changes to code at all, and therefore we’re pretty confident that nothing in this version could break anything. That said, it doesn’t mean that it’s impossible for the software to contain a bug from before somewhere, or that the issue is with the update, and not with the update process itself. If you are using premium add-ons, and are experiencing an issue, please contact us via our premium support channel.

Also, kindly note that when you rename a folder of an active plugin, that plugin becomes de-activated, which is a common way of re-gaining admin functionality in cases with fatal errors. Therefore, if you have re-named a folder of a WP RSS Aggregator add-on, that add-on may currently be inactive.

Brent,

In this comment, you mention that you’ve solved the problem by reverting to the previous version. However, I don’t believe that this was necessary.
Would you mind trying to manually trigger an update of the WP RSS Aggregator plugin? If you experience the same problem, please try following the instructions provided by our support staff, without uploading the old version. Either way, please let us know how it goes.

Xedin –

I don’t understand what you mean by a premium addon being deactivated. I noticed an update available for the core plugin to 4.9.1 so I clicked Update. Everything including the Keyword addon was working fine until immediately after updating the core to 4.9.1. I didn’t touch anything in the Keyword addon. That is, until my site went blank. Then I looked at the server logs and found a bunch of new PHP errors (all the same error). I simply renamed both the core WP RSS Agg plugin and the Keyword addon folders, and my site was up again. That’s as much info as I have. But, I find it interesting to see that Brent said he reverted to the previous version and was up and running again. Whether any code was changed in 4.9.1 or not, there is obviously a problem somewhere between the core and the addon. Or, perhaps – as you mention – a problem with the installation process.

Unfortunately in my case, I was actually online with the client/owner of that site to teach him how to accomplish something in a post, and while I was waiting for him to “catch up” with me, I went ahead and updated WP RSS Agg. You can likely imagine the conversation that followed. Well, I did immediately joke with him and said, “Oh no, what did you do?” He didn’t think that was funny. (Some people have no sense of humor.)

So, I guess I will contact the Premium Support Channel.

Thanks,
Jeff

jsafire,

As I explained earlier, when you rename a folder of a plugin that is active, and then access the site, that plugin gets de-activated. That is why the site goes up again – because the plugin, which causes the fatal error, is no longer active. So, if you would like to continue using the plugin afterwards, it must be activated again.

We are sorry to hear that some of the users of our plugins are experiencing issues while updating the core WP RSS Aggregator plugin. Unfortunately, we are still unable to reproduce this, as updates are happening normally for us, and all plugins stay active without errors of any kind. If you would like to help us find the cause of the issue, please contact us using the premium support channel, and make sure to attach the system info that is available on the RSS Aggregator > Debug page of the WordPress backend.

Xedin –

As I noted above that I will contact the Premium Support Channel to resolve this issue, I did not expect a reply. But, since you did reply, I think you may be confusing my post with Brent’s. Or, perhaps you simply did not understand mine.

I am obviously aware that renaming the folder will deactivate the plugin, which it the reason I renamed it – so I could get my site back up. Simple concept. If I now reactivate the core and Keyword plugins, the same PHP error occurs. So, your instructions that the plugins that were renamed must be reactivated is of little help as long as this issue (whatever it may be) still exists.

I think Brent and I have both explained the issue quite clearly.

I will now mark this topic as solved since I don’t think further discussion here is necessary.

Thanks,
Jeff

Hi Jeff,

Have you contacted us via the premium support channel yet? I believe we have not received an email from you. I have marked this thread as “not resolved” as we will use it as a public channel for updates on this issue, as well as for new feedback

Thank you.

Sorry, I can’t risk taking the site down again. Your upgrade seemed like a test of some sort anyway. Wish I could help you reproduce the error. Shoot me an email and I’ll reply with debugging info.

Brent,

We appreciate that you are concerned for the stability of your website. However, I must note that this is not a test. This release was made in order to update contributors and copyright information due to internal changes in our team, and as can be seen here does not contain any changes to the code at all, save for the version number in the constant value.

Please do drop us an email here with your system info. This could really help us understand the cause of this problem, and develop a solution.

Thank you for your patience.