huguetteinc

@jimleeder123 This is the first report like this I’ve heard of. What do you mean it was hacked? And how did disabling the plugin help the situation? Your feedback is very much appreciated.

Yes, it will work. It’s a custom field in your import:

https://www.wpallimport.com/documentation/custom-fields/mapping/

Thank you for the idea and the input. The plugin does indeed use server time, which would cause issues if your server and WP installation are not in sync.

Your fix would work but it would affect all time-dependent functions. This might not matter to you or me, but could have unintended consequences for other plugins.

I have explored using get_option(‘gmt_offset’) unfortunately WP time, user time, and server time are often not in sync, so I haven’t made any changes.

Can you explain what you mean by: “but the moment I go to the all post listing the exp date is cleared and the page show up again ??!!”?

Basically, after an expiration event the post should go from post status “published” to “draft” AND the expiry should be removed from your postmeta. The page will appear in your WordPress admin as a draft, but should not appear on your live site given that it’s a draft.

I don’t see what WordPress 5.1 would to do affect any of this, but I have to do a deeper dive into 5.1 and what changes it brought.

Right now the plugin is tested up to 5.0.3, but we are busy with some other work right now and will address updates to this plugin shortly.

Great to hear! Thanks for the kind words. If any feature requests or ideas come up, please let us know.

re time: That’s your WP time. The plugin uses your actual server’s time.

Expiration field is blank after the submitted change because the expiration date was before now(). When that happens the expiration action is considered to have been done and it’s removed from your postmeta. The plugin does not keep a log of expirations that have occurred.

My guess is that your server is not at UTC time, and rather at local time. When you put the expiration date in place it runs a check to see if the input time is in the past and keeps draft status if it is.

Because you are setting the expiry few minutes to a few hours ahead — but less then the time offset from your server time — the plugin sees the time as being in the past.

Sorry for the confusion. I realize this limits the usefulness of the plugin for some people and will be addressing it in future updates. It works well for our needs and is much simpler (though clearly less robust) then other methods.

That rating seems a bit harsh, but thanks for the feedback. We have CPT support coming soon. It’s an easy fix on our end, but its release is bundled with some much more complex additions to the plugin.

People have fixed this on their own if you are inclined:
https://www.ads-software.com/support/topic/great-plugin-working-for-cpt/

The plugin uses database functions as opposed to WP cron. It’s much simpler and does not require external dependencies or a specific server setup. Not all hosts support WP Cron, so this is a better solution for some people.

Post Expiration Date only handles post expiration based a calendar not a forward-looking time period (7 days in the future, etc). This is an easy addition and will likely addressed in a future version, but it’s not available right now. You’d have to manually pick a date/time 30 day in the future.

Yes, this is doable. I’m considering adding it in the next version or possibly in a paid version.

Questions:
– Would want it as a universal selection or on the post level?
– Would changing the category be useful or do you only care about post status?
– What plugin are you using now?

Tested more and this should be good. Please revert if you see further issues.

Yes, thanks for the feedback! This is on the roadmap, but I wasn’t sure on how useful it would be.

Can you explain your desired behavior? That upon expiration, rather than the status changing to “draft” the category would change to another category you’ve created. The post would remain live?

There shouldn’t be any problem with this. Are you using the “Universal” DateTime Selector in the Settings?

I’m on Windows + Chrome 70.0.3538.102 (Official Build) (64-bit) and seeing:
– the dropdown
– saved datetime after choosing my expiry
– “Exp. Date” in the posts listing page
– saved datetime when I return to the blog post.

Are you coming back to the post *after* the expiration? If that’s the case the expiration date will be purged.

Oh awesome to hear. Thanks for the follow up note, I was pretty perplexed by why this would have been happening.