Aaron Axelsen
Forum Replies Created
-
Fair enough – works for me!
I tried replicating this with your timezones and times on my dev server, but i can’t get the issue to reappear :/ .. are you testing on a development system or is there any way I could see this on your system?
I’m having trouble trying to reproduce this issue. Can you give me an exact example of when this happens? The exact date/time/etc that you are using to set the expired post?
You must be running multisite – I just made a change in the dev version that fixes the setting screen.
Do you actually know what the server time is? Are you hosting your own or using a provider? The above is just what wordpress is reporting.
What happens if you try loading this URL directly? /wp-admin/options-general.php?page=post-expirator.php
As for the timezone – I spent alot of time testing configurations and DST settings, so I’m surprised your seeing this. What is your wordpress and server/php timezone set to?
There is a “Post Expirator” menu item under settings.
@troy @oliverspies The 2.0.0 version currently in testing will support the ability to do different defaults and things for custom post types.
There is not currently a way to totally disabled it for a post type, but that could be added – please add that at http://postexpirator.uservoice.com/forums/176410-general
@kcharity The columns should show expires on? – they do at least in the 2.0.0 version
The issue you describe is corrected in the 2.0.0 release that is currently in testing – it should solve little issues like this.
There is really no clean way to do that. If the past posts are not expirated correctly, I think they will need to be manually taken care of. There is no way to know how an old post was suppose to be expirated – whether to delete or draft – and we can’t make the assumption to use what the default is currently configured as.
@sergeytru This is not a new feature – it does set the expiration date/time to be the same as the post time. What your describing is not currently part of the plugin
@brainoz thanks – it was due for an overhaul!
it has no impact on currently expired posts (other than renaming the meta value) – since they are already expired, and nothing had to be changed.
Any posts that are scheduled to expire in the future will have an event schedule for them at upgrade time.
the 2.0.0 plugin no longer functions this way – each “event” sets a unique cron event. More info and testing download at:
I would imagine that these issues will be fixed in version 2.0.0 – currently in testing, hope to roll it out later this week.
version 2.0.0 is in a testing state right now if you are interested in trying it out.
Alot of these oddities should be fixed in the 2.0.0 release – which I’m currently asking people to test.