I just tested a fresh plugin install on a fresh 3.4 install (single site) – and everything is working there.
The only reason you would get an error here “Reset Cron Schedule: Status: ERROR WITH FILTER” is if the plugin itself is not loading. This error comes up with the hook that adds the custom cron schedule is not loaded.
Do you have other plugins installed that might be conflicting?
Thread Starter
wroc54
(@wroc54)
This to me looks like the Post Expirator does cron entry options
I have a cron entries
wp_version_check
wp_update_plugins
wp_update_themes
polls_cron
wp_scheduled_delete
wp_scheduled_auto_draft_delete
and
DBC Backup
DBC Backup has not been updated in years, and only shows as compatiable up to 2.5.1
I would try removing that plugin and re-installing post expirator
Thread Starter
wroc54
(@wroc54)
I’ve installed post expirator but it still didn’t help.
How do I exactly add entry to cron and how should it look like?
the cron entry is automatically added via the plugin using hooks. So, if it is not working, there is likely something wrong with your wordpress install or some other horribly coded plugin that is conflicting.
Can you provide some more information about your environment setup?
Thread Starter
wroc54
(@wroc54)
whether the format of writing the date is important
option wordpress d/m/Y
post expirator d/m/Y
ad post 22.06.2012
I guess unfortunately I am not understanding your question.
If you are still having issues with the post expirator, please let me know some additional information about your server environment
Aaron,
Experiencing the same thing – continual admin notify message:
Post Expirator cron events need to be reset. Click here to reset
Can you just reset the cron events instead of displaying the message?
“Clicking here to reset” takes you to a page saying:
Reset Cron Event: Status: RESET NEEDED (red)
It looks like the cron event is missing, but that should be easy enough for you to add.
Could it be 3.4? Although I had the same problem under 3.3. Disabling and reactivating didn’t help either.
View debug logs is empty, even after enabling debug.
Ahhh – it’s fixed!! I needed to go into General options and save first. Once I saved, I could click Reset and it appeared to fix the problem. It seems your Reset button is not doing anything. If possible it’s best to get the fix to happen automatically without requesting the user reset the cron task. Happy to discuss offline.
Great plugin, looks like you’ve added some really nice features since I last looked at it, awesome work, thanks!
Thread Starter
wroc54
(@wroc54)
Aron,
this is about software and plugins
Thread Starter
wroc54
(@wroc54)
is it about used software and plugins ?
@brianoz if you are upgrading from older versions, its possible that there might be some reason why the cron needs to be reset. However, I cannot reproduce that issue on a fresh install of wordpress 3.4 with post expirator 1.6. Where you upgrading from previous versions or installing fresh?
As for the way the “reset” works – that is a good point, and it is confusing the way its currently worded. I’ll look at cleaning that up in the next version. The current behavior will display a link in the admin warning that will take you to the diagnostics page. Then on that page, you need to click the reset button by the cron event.
@wroc54 I’m still not 100% sure I understand your question, and without knowing specifics of your setup it is hard for me to diagnose.
If you are still seeing “Reset Cron Schedule: Status: ERROR WITH FILTER”, this would imply that there is something horribly wrong with your wordpress install, or possibly you have a corrupt file somewhere. The only reason this would show an error is if the plugin is unable to load in hooks from the wordpress core.
Thread Starter
wroc54
(@wroc54)
I have a problem with ajax
Please provide a complete step by step procedure to reproduce the problem you are experiencing. The more detailed you can be the better.
Thread Starter
wroc54
(@wroc54)
Thanks for your help. I’ve finally figured out what was causing problems. Apparently WordPress wiki plugin didn’t follow proper implementation of cron_schedule filters on http://codex.wordpress.org/Plugin_API/Filter_Reference/cron_schedules as they’ve reset whole array deleting also post-expirator entries. After disabling it post-expirator started t work correctly.
