andergmartins

Hi @slackarse thanks for the detailed report and solution provided.

We are planning another release this week and will include this new issue.

https://github.com/publishpress/PublishPress-Future/issues/318

Thanks

Hi @holylibor

Yes, that is the unix time. Please, what shortcode are you using?
Could you try this one?

[postexpirator type=date]

or

[postexpirator type=full]

Hi @foxylearning

Thanks for reporting the issue. That can happens when the filter the_content is called by a third party plugin when not in the main loop.

We opened a new issue here: https://github.com/publishpress/PublishPress-Future/issues/313

Feel free to follow the progress there, we are planning to release the fix on the next release.

Hi, thanks,

Please could you confirm you are still using WP 5.4? The line numbers changed a little.

Please, try this new package:

https://www.dropbox.com/s/kujayfn9o0drho1/publishpress-future-2.8.1-beta.2.zip?dl=0

Thanks,

Anderson

@mackensen Please, could you try the following beta package?

https://www.dropbox.com/s/oz7nyfa237f5o41/publishpress-future-2.8.1-beta.1.zip?dl=0

It packs a fix for this and will be available on the next stable release.

Actually, I’m sorry. I missed a detail and now I can replicate the bug with only Future activated. I’m debugging that one.

Hi @mackensen I tried to replicate but can’t see the same warnings using v2.8 on Wp 5.4.12. Please, could you let us know what is the endpoint you are calling in the REST api so we can try replicating the issue?

I know that disabling the plugin the error is gone, but please could you try disabling other plugins and leaving Future activated? That can help if Future is having compatibility with other plugins.

Thanks

@mikedrop1 please, what version number of MetaSlider are you using?

Hi guys,

We just released a new package addressing this bug.

Please, could you try installing v3.27.14?

Thanks

Hi @wattletales

Thanks for getting in touch and for reporting the issue.
We just released a new package addressing it.

Please, could you try installing v3.27.14?

Thanks

Hi @saintron,

Thanks for the information. We have a fix and we are planning a release next week.
Feel free to try the following beta package:

https://www.dropbox.com/s/qinqovn03pspamg/metaslider-3.27.13-beta.1.zip?dl=0

Thanks,

Anderson

Hi @lorigregor,

Please, could you try the following beta package?

https://www.dropbox.com/s/wyl596chxur5jka/publishpress-future-2.7.7-beta.1.zip?dl=0

Thanks

Hi @bwlazlo, I was checking and those error messages in the log might not be related to our plugin, or to the issue you reported.

Regarding the posts not expiring, please could you check if there are any cron event waiting to run for those posts?

Hi @lotuscorp It was released as 2.7.2 instead of 2.8.0. Current version is 2.7.3. We are double checking this issue.

• This reply was modified 2 years, 10 months ago by andergmartins.

Hi @shadician thanks for sending the debug log.

Pleaes, could you share the content of the Future > Diagnostics > Current Cron Schedule list? Do the dates appear correctly pointing to the future on the cron list?

Please, what version of the plugin are you using?