Aaron Axelsen

You could call this function:
_scheduleExpiratorEvent($id,$ts,$opts)

You would pass in the ID of the post, the UTC timestamp of the expiration date, and an associative array of options to specify the settings. If you look through the expirationdate_update_post_meta function it should give you a good idea.

It sounds to me like it’s a problem with how you are saving the expiration date information with the auto generated content plugin.

What code are you using to save and store the post expiration value?

The value is stored as a GMT/UTC timestamp value in the post meta data. Keep the timezone in mind when setting up your query. So if you craft your query correctly, I don’t know why it wouldn’t work.

Good Luck!

If you were editing with “Quick Edit”, there was a bug that was setting it back to draft. That will be fixed in the next release – 2.3.0. Stay tuned!

Feel free to drop this as a suggestion. If there is a huge demand for this, i’ll certainly consider it!

https://postexpirator.tuxdocs.net

Can you please restate your question? I’m not following.

Is this happening when you load the “Post” page? Or what post type is triggering this error for you?

What happens if you create a brand new post, and set the expiration options? What shows in the debug log for that post?

The default expiration setting will only work on new posts or posts that are edited. You can’t just change the setting and expect it to retroactively work on all past posts – it doesn’t work that way.

As for the Cron, the Post Expirator plugin relies on the built in WordPress WP-Cron process. The check in the plugin simply checks to see if that appears to be loading.

If you make a new post, and set an expiration option, is that working correctly?

@capi81 you are correct! Thanks for the catch, we’ll get this fixed up!

@lingenchan you can enable it on the Diagnostics tab

Good Luck! If you don’t get anywhere, and are seeking out other hosts drop me a message and I can assist there as well! https://thirstylemur.com

It sounds like the host you are on does not support WP-Cron if you are also required to use the WP Missed Schedule plugin. Post Expirator relies on the WP-Cron process to actually carry out the scheduled events.

Which hosting provider are you using? If you google around, there are several links out there an setting up alternative options to trigger the wp cron interface for hosts that have it disabled.

The plugin works great and a number of people use it on a regular basis. Please provide some additional detail on how you have it setup, what you are trying to do, and what is not working and I’m sure either myself or someone else on the forums will try to help you out.

Can you send a screen shot of what you are seeing?