Updating the YARPP Plug-in Wiped Out My Site

I renamed wp-content/plugins/yet-another-related-posts-plugin by wp-content/plugins/yet-another-related-posts-plugin1 and now runs again.

same as above and all ok now!!!!

@marom both renaming & deleting should work This is standard advice for any plugin misfire.

Also doesn’t hurt to open a new browser as the caching on the one you were using might not show the changes straight away

Great, thanks @jason, much appreciated.

Okay, renaming worked for me, too, but I do not understand why renaming a file changes the way it operates.

@wayfaringranger renaming a plugin means it can not run. It is the equivalent to deactivating the plugin.

Usually you can’t deactivate the plugin because you can’t get into the WordPress admin so going in at the file level works.

Deleting the plugin also works but you probably want to reinstall the plugin later on ( if/when it gets fixed – or updated). Most plugins write back fields and content to the main WordPress db.

Some plugins have an un-install function and that should clean the content out of the main db. Deleting a plugin shouldn’t lose that other content but you wouldn’t want to uninstall.

Someone else will know more about the connection between deletion and an uninstall process. I don’t believe there is one.

But if you had a rogue plugin that was causing issues you would want to delete it AND almost certainly clean out those files on your main WP database.

But in a situation like this – just want to deactivate and that preserves the settings and other content for later. ( Once you are back into WordPress admin then you can rename the plugin back to the original and keep it deactivated till a fix has been made.)

We just pushed out YARPP 4.1.1, which fixes an incompatibility with PHP prior to 5.3. Please upgrade to this latest version. Thanks for supporting YARPP and sorry for any inconvenience!

Wow that was quick. Thanks!

Thanks Jeff,

Most of my sites are on PHP 5.3 or later so I wasn’t able to test for the error on another site.

Same as Jason with my sites. I can verify that 4.1.1 works with PHP 5.2.17 and the WP 3.7.1

Great feedback! Thanks, guys!

Thank you very much for fixing this so quickly!

@wayfaringranger you should be able to do the update now & if it is fixed – then you can change this topic to resolved as we can’t do that.

P.S it looks ok to me on the sole PHP Version: 5.2.17 – ( bad luck for me)

I have asked the hosting company to look at moving that site to a PHP ver of 5.3 or later version like all the other sites I look after ??

@jason Kemp, thanks for your assistance. I am a rookie and need all the help I can get . . . . ??