Aaron Axelsen
Forum Replies Created
-
Yikes – it appears something went horribly wrong – did you also upgrade the wordpress core?
I think I would suggest reinstalling the core WordPress files. If it was a plugin issue, it shouldn’t be acting how the site currently is.
WordPress by default disables error logging – so you may need to turn that on if you are looking to debug it further.
Do you have your timezone set correctly in your installation?
Thats what I get for typing too fast – glad your set!
This information is in the changelog – the meta_key was renamed to _expiration_date
This is likely not related to the the post expirator plugin.
Try removing the file “.maintenance” in the root wordpress folder – this usually solves this issue when an upgrade gets stuck
There will be a single task for every post that is set to expire in version 2.x. So, if you have 20 posts scheduled to expire, there will be 20 tasks .. does that clear it up?
@ericekidwell what version of the plugin are you running? What does the debug log tell you? Can you define “not working” in more detail?
Can I ask why you are not using the built in wp-cron? How are you running it otherwise?
The post expirator and wordpress crown both operate in GMT/UTC time – so, it sounds like there is something weird going on with your server/timezones.
Can you let me know the follow:
1) What is your PHP default timezone?
2) What is your server timezone?
3) What is your wordpress timezone string configured to?I’ve reached out to Tareq and will see what I can do to assist in making these two plugins play nice again.
I don’t know how your trying to do the expiration, but you cannot just add in a custom field and have it work anymore. The 2.x version of the plugin changes how this works and there is now an event schedule for each post expiration to conserve system resources.
Feel free to add it to the uservoice site – http://postexpirator.uservoice.com
It’s the only way I can keep track of all of the feature requests
I think this feature request is what your after:
If not – feel free to add another
right now it only supports the “categories” taxonomy. I’m still thinking through the best way to add support for other taxonomy types.
Just published 2.0.0