Title: Dead Plugin?
Last modified: August 21, 2016

---

# Dead Plugin?

 *  [ciordia9](https://wordpress.org/support/users/ciordia9/)
 * (@ciordia9)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/)
 * Looking at the history of posts it doesn’t look like the author has checked in
   since his last release 3mo ago. Has anyone been in touch? Looks like the plugin
   might have expired (pun intended.)
 * Looking at alternates doesn’t find any active either–has anyone found one reliable?
 * [https://wordpress.org/plugins/post-expirator/](https://wordpress.org/plugins/post-expirator/)

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

 *  [Aaron Axelsen](https://wordpress.org/support/users/axelseaa/)
 * (@axelseaa)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066671)
 * Just because I haven’t updated the plugin in 3 months, doesn’t mean its dead ….
 * I still actively us it on my sites. What issues are you seeing?
 *  [hidalgor](https://wordpress.org/support/users/hidalgor/)
 * (@hidalgor)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066704)
 * @AaronAxelsen great plugin.
 * Quick question – I would like to implement a conditional statement. Example scenario:
   If a post is about to expire but the post reach a number of views the post will
   not expire.
 *  Thread Starter [ciordia9](https://wordpress.org/support/users/ciordia9/)
 * (@ciordia9)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066715)
 * Sorry Aaron, some people were finding bugs and working around them, sharing solutions
   and walking away for 3mos can be construed as a potential–or early abandonment.
   Remember net years are like dog years, heheh!
 * As a person who was about to invest some time in your solution I wanted to find
   out if you really were around or not to continue this path. I’ve had a number
   of things recently I’ve had to rework entirely due to abandonment.
 * I saw no harm for asking it but I do apologize if I have offended.
 *  [leonsokov](https://wordpress.org/support/users/leonsokov/)
 * (@leonsokov)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066773)
 * Hello there, any idea why the plugin is not working with wordPress 3.9.1?
    Thanks
 *  [Robin Li](https://wordpress.org/support/users/hellfire6969/)
 * (@hellfire6969)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066776)
 * Do not working for me as well, I had checked the debug log, it showing different
   time zone and unscheduled error, see below, would you please check this?
 * 2014-07-07 17:01:30 13324 -> SCHEDULED at Mon, 07 Jul 2014 17:10:00 +0000 (1404753000)
   with options Array ( [expireType] => private [id] => 13324 )
    2014-07-07 17:01:
   30 13324 -> EXISTING FOUND – UNSCHEDULED 2014-07-07 16:59:47 894 -> SCHEDULED
   at Tue, 08 Jul 2014 00:30:00 +0000 (1404779400) with options Array ( [expireType]
   => draft [id] => 894 ) 2014-07-07 16:59:47 894 -> EXISTING FOUND – UNSCHEDULED
   2014-07-07 16:58:50 13324 -> SCHEDULED at Mon, 07 Jul 2014 17:10:00 +0000 (1404753000)
   with options Array ( [expireType] => draft [id] => 13324 )
 *  [J-ME](https://wordpress.org/support/users/j-me/)
 * (@j-me)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066808)
 * After upgrading to WordPress 3.9.1 I found that this plug-in stopped working.
   One of the issues I found is not necessarily with the plug-in itself but with
   the WordPres Cron jobs not executing. Some of our sites do not actually receive
   enough direct traffic to trigger the cron job when the home page is accessed,
   as we use JSON Feeds to update another site with published posts.
 * The work-around I found was to force a scheduled load of the home page by using
   a system CRON job (or Windows Task if using Windows) to force the WP Cron job
   to kick in.
 * This appears to have resolved our problem of posts not expiring as scheduled.
 *  [J-ME](https://wordpress.org/support/users/j-me/)
 * (@j-me)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066832)
 * An update to my previous post about this plug-in. It seems that forcing the WP
   Cron job helps but we as still experiencing problems with posts failing to expire.
 * I’m guessing this is a dead plug-in as it seems the author hasn’t responded to
   anyone about the issues.
 * Does anyone know of an alternative plug-in?
 *  [frungimi](https://wordpress.org/support/users/frungimi/)
 * (@frungimi)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066874)
 * What link are you loading to manually run the cron?

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

The topic ‘Dead Plugin?’ is closed to new replies.

 * ![](https://ps.w.org/post-expirator/assets/icon-256x256.png?rev=3569472)
 * [Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories](https://wordpress.org/plugins/post-expirator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/post-expirator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/post-expirator/)
 * [Active Topics](https://wordpress.org/support/plugin/post-expirator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/post-expirator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/post-expirator/reviews/)

 * 8 replies
 * 7 participants
 * Last reply from: [frungimi](https://wordpress.org/support/users/frungimi/)
 * Last activity: [10 years, 11 months ago](https://wordpress.org/support/topic/dead-plugin-4/#post-5066874)
 * Status: not resolved