Aaron Axelsen
Forum Replies Created
-
Can you try the latest version and let me know if that solves your problem?
This has been recorded here for future consideration: https://postexpirator.uservoice.com/forums/176410-general/suggestions/4070810-add-a-method-to-expire-programatically-or-detect-a
Just out of curiosity, how did you install WP initially?
Can you let me know what other plugins you have activated on your blog?
This will of course be fixed in a upcoming point release!
Go to the “Settings” page, and choose the “default” tab. Save that page and the problem should go away.
On what page(s) are you getting this error? Is it only after a certain operation?
I believe this issue should be fixed in 2.1.0, which has just been released.
I believe this issue should be fixed in 2.1.0, which has just been released.
I believe this issue should be fixed in 2.1.0, which has just been released.
If you look through the plugin code, I did break out the scheduling bit into a function (_scheduleExpiratorEvent) that you could in theory call yourself with the correct arguments.
The version I have in dev allows to set various settings for different post types. I have been debating also adding an option to disable the widget from even appearing on certain post types if its not needed. I will see if I can get this implemented before the next release.
Just so I don’t forget, you can add it to the list http://postexpirator.uservoice.com
You can add this to the feature request site. It could be done by adding another option on the backend.
In this case, when you go in to manually change the category you should also uncheck the “Enable Post Expiration” box, it should unschedule and remove the cron event.
entering something like “+90 days” should do the trick. the strtotime function takes literal strings like the above and translates them into the necessary formats.