Plugin de-activates upon upgrading due to main filename change
-
The plugin de-activated itself when I updated it to the latest version. This is apparently because the main plugin file has been renamed, and hence the old name which is in WP’s list of active plugins, can no longer be found.
Of course, if the next release reverses this change it’ll then hurt people who re-activated the changed version. You might want to carry both files, with one being a simple require() of the other.
- The topic ‘Plugin de-activates upon upgrading due to main filename change’ is closed to new replies.