andergmartins

Hi @lotuscorp, thanks.

Regarding the time, I see that the log is currently using the raw time from on the server, not considering the site’s time zone. This can be confuse, but the correct would be always store GMT time for logs.

Is the expiration set to unpublish the post or remove categories?

Hi guys,

We released a new version fixing the issue. Please, try updating to v3.15.1.

Thanks

Thanks guys,

We are doing a new release and will be available soon.
Sorry for the inconvenience.

@dependencyinjection yes, you can install the following package:

https://www.dropbox.com/s/bym3uwjorqdpndf/publishpress-authors-3.15.1-alpha.1.zip?dl=0

If you already have v3.15.0 installed and still see the issue, please, try the following package:

https://www.dropbox.com/s/bym3uwjorqdpndf/publishpress-authors-3.15.1-alpha.1.zip?dl=0

Please, could you let us know the results?

Thanks

Hi @bartoszwojciechowski
Thanks for reporting that issue. Please, could you confirm what version you are using? We released twice today.

Are you using v3.15.0?

Please, could you double check if you have Authors installed twice?
What PublishPress family plugin you have installed?

Thanks,

Anderson

Awesome, thanks for the feedback and for helping us, guys.

Thanks guys for the feedback.
Please, could you try the following RC package?

https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0

Thanks,

Anderson

Please, could you try the following RC package?

https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0

If you still have the issue, please, could you send us the metadata of the post that are prefixed with “_expiration-“.

Thanks,

Anderson

Thanks guys for the feedback.
Please, could you try the following RC package?

https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0

If you still have the issue, please, could you send us the metadata of the post that are prefixed with “_expiration-“.

Thanks,

Anderson

Thanks guys for the feedback.
Please, could you try the following RC package?

https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0

If you still have the issue, please, could you send us the metadata of the post that are prefixed with “_expiration-“.

Thanks,

Anderson

Thanks guys for the feedback.
Please, could you try the following RC package?

https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0

If you still have the issue, please, could you send us the metadata of the post that are prefixed with “_expiration-“.

Thanks,

Anderson

Thanks guys for the information.

@syntax53 please, could you check the old post that is showing the expiration chckbox enabled, and let us know what are the metadata (only the ones prefixed with “_expiration-“) for that post?

@jkorte The issue 1. is confirmed and should be fixed on the next release.
2. That is possible. Please, could you check the metadata (“_expiration-…”) for one of those posts you see the issue?

Thanks

@cranewest thanks for the information.

Sorry, but maybe we were talking about different bugs.
The bug we consider that is fixed (according to our tests) is related to the UI, where the checkbox to expire posts was always enabled.

If you see posts that are expiring automatically without touching the post, that is probably caused by cron events that are still scheduled for those posts. Maybe that is a leftover of an old bug. We fixed the UI, but the cron events we can’t fix automatically because you are not able to know what posts you really want to expire and what should not expire.

Please, could you check the diagnostics page: Future > Diagnostics > Current Cron Schedule. The post IDS are in the Arguments / Schedule column.

Thanks, guys! We are trying to replicate it but we can’t see the issue anymore on v2.7.1.

Please, could you try cleaning up the browser cache before trying again?

Please, does that happen only when you save the post using the post editor? Or does that happen if you try to quick-edit the post?`

Guys, I’m trying to replicate it but we can’t see the issue anymore on v2.7.1.

Please, could you try cleaning up the browser cache before trying again?

Please, does that happen only when you save the post using the post editor? Or does that happen if you try to quick-edit the post?