Title: Plugin Upgrade Failure
Last modified: August 20, 2016

---

# Plugin Upgrade Failure

 *  Resolved [jon](https://wordpress.org/support/users/adiant/)
 * (@adiant)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-upgrade-failure-1/)
 * On a test site running WordPress 3.4-RC2-21036, I updated my own plugin (which
   is in the repository) to the latest version and it generated a fatal error to
   the effect that it could not find the main .php file. Doing the same plugin update
   on WordPress 3.3.2 works perfectly.
 * Unfortunately, I thought it was my plugin at fault so did not capture the exact
   error message, and I don’t know how to reproduce the problem.
 * Here is my best summary of what is wrong with 3.4RC2: automatic update of a plugin
   where the main .php file has been renamed from one plugin version to the next,
   will generate a fatal error on activation.
 * Workaround: uninstall and reinstall the plugin.
 * Plugin in question: [http://wordpress.org/extend/plugins/jonradio-display-kitchen-sink/](http://wordpress.org/extend/plugins/jonradio-display-kitchen-sink/)
   
   Upgrade from 1.0 to 1.1 corrects the name to jonradio-display-kitchen-sink/jonradio-
   display-kitchen-sink.php from jonradio-display-kitchen-sink/jonradio-kitchen-
   sink.php

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-upgrade-failure-1/#post-2803774)
 * You can reproduce that probably by installing the old version and then the new,
   but I’m willing to bet that’d happen on any version of WP.
 * Don’t rename the main plugin file unless you have to 😉
 *  Thread Starter [jon](https://wordpress.org/support/users/adiant/)
 * (@adiant)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-upgrade-failure-1/#post-2803807)
 * Excuse my ignorance, but I’m not aware of any way to install an old version from
   the plugin repository. I have, however, made several attempts to load the previous
   version of the plugin via FTP from my own backups, and then let it update automatically.
   They all work, with both beta and the current production version of WordPress.
 * My best guess is that this was a plugin repository issue, i.e. – for a short 
   period after I’d updated the repository with my new version.
 * As a result, I’m closing the issue.
 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-upgrade-failure-1/#post-2803812)
 * Normally people use tags to mark a completed version, and that makes it very 
   easy to get the older versions.
 * [http://wordpress.org/extend/plugins/akismet/developers/](http://wordpress.org/extend/plugins/akismet/developers/)
 * If you make a tag folder for each version, then revision and integration testing
   is much easier 🙂
 *  Thread Starter [jon](https://wordpress.org/support/users/adiant/)
 * (@adiant)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-upgrade-failure-1/#post-2803813)
 * Thank you for that info!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Plugin Upgrade Failure’ is closed to new replies.

 * In: [Alpha/Beta/RC](https://wordpress.org/support/forum/alphabeta/)
 * 4 replies
 * 2 participants
 * Last reply from: [jon](https://wordpress.org/support/users/adiant/)
 * Last activity: [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-upgrade-failure-1/#post-2803813)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics