Aaron Axelsen
Forum Replies Created
-
I think what you are asking is that you have a single post that is assigned to more than 1 category, but you want each of those categories to expire at a specific time?
If that is the case, there is not a way to do that. And I’m not sure how a feature like that could be easily implemented either.
If you enable category expiration and set a category, it will stay published. Setting the category expiration does not change the status, only the categories.
This may be a silly question, but have you verified that the time / date on your host system is correct?
Take a look at the development version – I believe all of these and a few others are addressed.
I have implemented some tweaks in the dev version – take a look and let me know if it works and does the trick for you.
The start time should always be in the past. Then, one wordpress fires it once, it changes the time to be the next time it will run. That is why it changes after a page load (and a successful cron event).
Now, if you are saying that time never changes, that is curious. Does the debug show the plugin firing?
Glad you got it working! Hopefully other plugin can correct their implementation.
This plugin originally was only available to run every hour. There was actually a huge demand for it to expire on the minute, which is one of the reasons why it was changed. I would likely keep “minute” as the default, and look at having an option to use hourly.
This will required a good amount of changes/testing, so it will be a bit before it’s ready. If you are willing, once I get it in a “beta” worthy state, I can shoot a link over for testing.
I always have resources usage in my mind, and do what i can to minimize unnecessary db calls, etc.
I’ll probably re-work the cron entry check, and keep it as an admin side only checked. Because if something is screwed up with the cron scheduled, its likely any additional events to check the schedule would also be hosed.
Please provide a complete step by step procedure to reproduce the problem you are experiencing. The more detailed you can be the better.
@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.
@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.
The plugin by design is set to run every minute. Now, are you looking to run this on a multisite network or just single hosts? Because I could look into adding an option to select, but that wouldn’t address your concern if users can select this themselves.
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
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?
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