Aaron Axelsen
Forum Replies Created
-
you can set a default expiration value .. so when you create the post, it will have a default value set
Not currently – feel free to add to the feature request site http://postexpirator.uservoice.com
WordPress should automatically take care of the cron for you. The info you have there seems to be for system cron, and very old
You do have it set to only expire posts once a day. If you want it to expire more often you can change that to run every minute or hour.
This is an issue that i’m kept in the back of my mind – I hope to have a solution for it in the future
You have quite a few items in your cron – it may not be functioning correctly .. i’m concerned with the multiple upgrader_scheduled_cleanup entries
There is another way to get ride of this be changing the caps. I need to add this as an option into the plugin yet.
debugging is something I hope to add more of in the future – there is not really an easy way to debug currently, other than echoing variables at key times
Nice catch – will get this added in.
Please give version 4.0 a shot. It has been reworked to not require installation in the mu-plugins folder. Though, it still requires a MultiSite WP installation.
@kennibc thanks for keeping tabs on the requests here! And again, you are correct.
Correct – it is not designed to work with single user installs.
There is a shortcode – does that help any?
The plugin currently stores the expiration date as a unix timestamp in the custom field “expiration-date”. So, in theory – yes.
Usually when there is an error with the filter, it means another plugin you are running is not correctly implementing cron rules. I would imagine your tweet import hook is likely the culprit