jkorte
Forum Replies Created
-
Thanks. Will do. Is this the correct link/version?
https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0
@andergmartins I don’t have permissions beyond the WP dashboard (content editing) and can’t retrieve the meta you requested. Sorry.
- This reply was modified 3 years, 1 month ago by jkorte.
Since the plugin update (we’re on 2.7.1) we continue to have this issue. A couple observations:
1. We see many “cron event not found” msgs in the posts list for recent posts assigned an expiration. The fix needed is to uncheck “enable post expiration” > update the post > recheck “enable post expiration” (choose the desired date/time) > and update. And hope that’s the end of it. Note that for us, these steps do not ‘stick’ when using quick edit and have no effect. I confirmed this is a recent issue by checking one of our dev sites that has version 2.6.2 installed. None of the same posts in this dev site display “cron event not found.”
2. We often use Yoast Duplicate Post and have since the site launched. Could it be that duplicating previous posts is bringing along ‘old pre-2.7’ code that does not play nice with the latest plugin version? Just a thought.
We have the same issue (using 2.7.1) This did not happen before the “name-change-only” update.
Auto-enable is OFF for all post types. But when opening post to edit, the auto-expire is “on” and the date/time of expiration is precisely when the post is opened to edit.
We have the same issue (using 2.7.1) This did not happen before the “name-change-only” update.
Auto-enable is OFF for all post types. But when opening post to edit, the auto-expire is “on” and the date/time of expiration is precisely when the post is opened to edit.