mmihelic

Thanks, I will try that.
In the meanwhile I added the following code to the end of wp-settings.php:

add_filter('upload_mimes', 'pixert_upload_types');
function pixert_upload_types($existing_mimes=array()){
        $existing_mimes['swf'] = 'application/x-shockwave-flash';
        return $existing_mimes;
}

Not really, no. Unless you wrote some code to just remove that RSS widget, or to have it check if it was running from the same domain and, if so, to error out.

I was afraid you’d say that.
Thank you for the confirmation.

Kind regards,
mmihelic

Thank you for your answer Mika. Please see the following text for my answers.

Was this calling an RSS feed from another site on the network?

The user put an RSS widget into the footer to show latest posts. Please do not ask me why they did it. I do not know ??

If so, this is a terrible idea.

I agree.

It crashed because you created a recursive loop on your site.

Yes, the user’s action caused a recursive loop. I wrote something along those lines in my initial post.

The fix is don’t call links like that between sites.

Unfortunately this is not up to me. Our network has about 3000 users on it and well, as you can imagine, there is much potential for error in such a large number.

Are you trying to show posts from one site on another?

I suppose the user wanted to show the latest posts from their site. Why they did not use a widget that does that, they used the RSS widget instead. Why I do not know ??

The question still remains, is there a way to protect against this?

Kind regards,
mmihelic

Please disregard this post, I wanted to correct a spelling mistake after it was already posted.

Confirming it is still broken in 3.9.1.

—
mmihelic

I was afraid that would be the case ??
And at the same time hoping there was already a plugin for that.
Thank you Mika.

Thank you for the suggestion, I have already tested the plugin. It looks like it can either enable or disable user access to the plugin. This is not the desired result. I noticed I did left out a bit of information.
We want the users to see the old plugin so they can deactivate it, since the new plugin will activate only if the old one is deactivated. Once deactivated, users would not be able to activate it back. If the plugin is hidden from the users, then they cannot do that.

For plugin visibility we are currently using a modified version of Exclude Plugins.

The plugin works by intercepting the WP error messages and acts acordingly. These messages are hardcoded in the plugin. That is why it only works for the English language.

I updated it do accept translation files.
You can download the updated version here.

I could not find any way of contacting the authors before posting this so I hope they read this post and incorporate che changes into the official plugin version.