andergmartins

Hi @leighfarrior

Thanks for the information and the screenshot. I tried replicating that error but the free version of your theme and Future (on a fresh site) do not trigger that error.

Please, could you check the browser console when that error is displayed? We will need a little more context. Please, could you send us screenshots showing all the errors displayed in the console?

Hi @lucvangerrevink-1

Thanks for the information. We are planning to make a new release next week with the fix for this issue.

Hi @chemboy,

The expiration month is only available as a unix time data in the _postmeta table, on a register with meta key “_expiration-date”.

For getting the month on a raw SQL query you can use the function from_unixtime:

SELECT FROM_UNIXTIME(meta_value, "%m") as month FROM wp_postmeta
WHERE meta_key = "_expiration-date"

But we are working on a new version of the plugin that implements a new queue for the events, based on the library Actions Scheduler and the data will be saved in a different table.

Please let us know if you have any further questions.

Hi @erwinbr thanks for reporting that. We are working on a fix for that as well. We will keep you posted.

Hi @maudits if you plan to use any currently available expiration actions, and want to update the meta value after it expires, that is possible using the action publishpressfuture_expire. That is the action that triggers the post expiration. You can hook directly into it using a priority number higher than 10, so you will be sure it runs after the post expires. But that action was not intended exactly for that, so it won’t provide any confirmation about the success of the process. You should create a check by yourself, checking if the post was indeed expired. This action passes 2 params: $postId and $force. Since you are not triggering it, but listening it, you can use just the first one to know what is the post being expired.

In case the “post expiration” you expect is not related to taxonomy or post status change, but just changing the meta value, that is not currently supported. On this case the only way right now is choosing any expiration action and reverting it by yourself after it happens, using the same hook I mentioned here.

I added 2 new discussions for feature requests that might be interesting to you.

https://github.com/publishpress/PublishPress-Future/discussions/384

https://github.com/publishpress/PublishPress-Future/discussions/383

Feel free to go there and upvote or comment.

Hi @rrenault thanks for reporting the issue and suggesting the fix.

I have fixed it for the next release, you can follow this issue: https://github.com/publishpress/PublishPress-Future/issues/337

Thanks

Awesome, thanks guys for the feedback and for the help.
Please if you see a similar issue again, please open a new thread and linking this one.

Ok, sorry for another beta package, but I think it will fix the warning and fatal error you found @pepe80

https://1drv.ms/u/s!AsIYGyKS9Y3Ym2l4lHAZeQx3fSnW?e=MXHryS

Thanks @pepe80 I will check the error and the log

Guys, please could you try the following beta package? There are some changes in the expiration code and in the log. I hope we have a little more details in the log if you still see the error.

https://1drv.ms/u/s!AsIYGyKS9Y3Ym2g6KTAo3h4qkGCw?e=kjaClI

Please, could you check if you see any meta expiration_log for the expired post?

Thanks for the details guys.

I see now that if I schedule a post to expire in the future and run wp cron event run --all it will not check the date and expiration action will run, and after running, it is removed (by design). The same thing don’t seem to happen if I run that command with --due-now.

The wp cron system has the autonomy to execute the action, and will always delete a task after running it, no matter an error occur.

But I do see the PROCESSED registers in the log.
I’m debugging to find more information. Please, let us know if you find out any new pattern for this.

@chamois_blanc there are 2 events on that screenshot because they are scheduled for 2 different posts.

Hi @jodunningevents and @pepe80 thanks for reporting the issue. Please, could you try the following beta package?

https://1drv.ms/u/s!AsIYGyKS9Y3Ym00fGvrWO-_HpxlN?e=HQi7Tm

Thanks

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]