Title: Are non-current plugins a problem?
Last modified: August 22, 2016

---

# Are non-current plugins a problem?

 *  [hedera](https://wordpress.org/support/users/hedera/)
 * (@hedera)
 * [11 years, 7 months ago](https://wordpress.org/support/topic/are-non-current-plugins-a-problem/)
 * Our site, [http://lifering.org](http://lifering.org), currently runs WP 3.9.2.
   In the last week I’ve run into at least 3 plugins that are not certified to this
   version; some of them are backleveled as far as WP 3.5.x.
 * Is this something I should worry about? I’m particularly concerned about iThemes’
   _BackupBuddy_, which we pay for; I have an open question in their forum. We now
   have a second update in version 5.x and neither 5.x update has been certified
   with 3.9.2. Other plugins I was considering using were the _WordPress HTTPS_ 
   plugin (certified to 3.5.2), and VelvetBlue’s _Update URLs_ plugin (certified
   only to WP 3.8.3).
 * I’m generally much more comfortable updating a plugin which says it’s certified
   on my version. Am I being too sensitive? How far backleveled is too far?

The topic ‘Are non-current plugins a problem?’ is closed to new replies.

 * 0 replies
 * 1 participant
 * Last reply from: [hedera](https://wordpress.org/support/users/hedera/)
 * Last activity: [11 years, 7 months ago](https://wordpress.org/support/topic/are-non-current-plugins-a-problem/)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics