Comments on: If Plugin Deactivation Breaks Your Blog

By: According To John » Blog Archive » If Plugin Deactivation Breaks Your Blog

Sat, 07 Jun 2008 19:34:25 +0000

[...] If Plugin Deactivation Breaks Your Blog According to John Lamansky, the reason this error occurs is because the theme is still calling on the plugin you deactivated. [...]

By: Weblog Tools Collection » Blog Archive » Plugin Deactivation Issues Solved With Actions and Filters

Sat, 07 Jun 2008 09:45:32 +0000

[...] subscribe to our feed! You can also receive updates from this blog via email.When Jeff wrote about plugin deactivation breaking your blog, Aaron and I wrote in the comments of a few solutions to prevent plugin issues with [...]

By: Ronald Huereca

Ronald Huereca — Sat, 07 Jun 2008 06:58:00 +0000

@Stephen,
I have a post going live in a few hours that should hopefully answer your questions.

By: When A Deactivated Plugin Breaks Your Blog

When A Deactivated Plugin Breaks Your Blog — Fri, 06 Jun 2008 21:17:59 +0000

[...] logged into my dashboard and saw a post in the WP feed about what to do if your blog goes down upon deactivating a plugin. I’ve had this happen to [...]

By: Stephen R

Stephen R — Fri, 06 Jun 2008 19:52:58 +0000

Sorry… meant to say “Ronald or Aaron” in that comment.

By: Stephen R

Stephen R — Fri, 06 Jun 2008 19:51:36 +0000

Kevin or Ronald –

Might either of you be so kind as to bang out a post giving an example of what you’re referring to with “do_action”? If it’s a good idea, it’s an idea worth sharing.

By: Claudia J.

Claudia J. — Thu, 05 Jun 2008 02:42:34 +0000

I may be the only one, but deleting the plugin never actually worked for me whenever turning it off broke my theme. I always had to go and delete the code from the theme like the linked to article says. Weird.

By: arbitrarymarks.com » Blog Archive » links for 2008-06-04

arbitrarymarks.com » Blog Archive » links for 2008-06-04 — Wed, 04 Jun 2008 07:35:12 +0000

[...] If Plugin Deactivation Breaks Your Blog (tags: blogs.coding) [...]

By: Teli

Teli — Sun, 01 Jun 2008 23:49:07 +0000

As a theme creator, if I code a theme to be dependent on a plugin (rarely), or even when making concession for people who may be running an older version of WP which doesn’t have all the fancy new functions, I always make sure to include a default if function exists check first.

It’s just a good habit to get into when producing themes for public consumption.

By: Ronald Huereca

Ronald Huereca — Sun, 01 Jun 2008 23:08:27 +0000

@Aaron,
Yes, that’s a good point. If authors added the appropriate actions and filters, all that would be required is a bunch of do_actions and apply_filters, and it wouldn’t break themes if the plugin was gone.

By: Aaron

Aaron — Sun, 01 Jun 2008 22:32:55 +0000

Function_exists() are messy. More theme authors need to add do_actions as these are automatically tested for existence before they are called.

They also fit better into WP themes.

By: Ronald Huereca

Ronald Huereca — Sun, 01 Jun 2008 21:00:14 +0000

A lot of plugin authors are to blame as well, because when showing how to use the plugin in a template, the usually don’t supply the ‘function_exists’ code, which will solve almost all deactivation issues.

By: Kevin Paquet

Kevin Paquet — Sun, 01 Jun 2008 20:57:12 +0000

For me, just deleting a plugin worked out 100% right now. Haven’t experienced such kinds of errors that often.
What really was something of my concern was the Maintenance Mode Plugin that was active and my site in maintenance that time. And I was upgrading to 2.5 that time. I wasn’t able to get into my blog until I figured out that deleting/renaming the plugin folder would help

By: Tom

Tom — Sun, 01 Jun 2008 20:36:20 +0000

i’ve experienced this pretty often, but not when deactivating a plugin, but rather when implementing a theme that is depending on certain plugins. This already gave me the suggestion that the error was related to plugin. The post does not really apply to me, but still interresting to discuss.