We use Gutenberg as well and have the issue as well as Ray in all browsers (also in private mode).
There’s a lot of random feedback being posted here without any useful details included.
If you want to help debug this for your site, please post 3 things:
1. Use a plugin like this to rollback to an earlier version: https://ww.wp.xz.cn/plugins/wp-rollback/. What specific versions do work correctly?
2. Disable other plugins one-by-one. Is there a plugin conflict here?
3. Share a screenshot of your “Defaults” and “Post Type” settings.
I did #1 earlier. Here are my screenshots. I don’t have time to do #2 right now.
defaults: https://drive.google.com/file/d/185o07eNz1loyxocupZJ65aOuiE8S-UMA/view?usp=sharing
post types: https://drive.google.com/file/d/186D4WwXFxP8YYV-_CkPntX6fiFnXq67L/view?usp=sharing
Here are the debug logs at the last automatic delete:
2022-01-22 13:30:18 77 -> NO PAYLOAD ON SAVE_POST
2022-01-22 13:29:02 77 -> PROCESSED delete Array ( [expireType] => delete [category] => [categoryTaxonomy] => [enabled] => 1 )
2022-01-22 13:28:44 77 -> SCHEDULED at Sat, 22 Jan 2022 13:22:00 -0500 (1642875720) with options Array ( [expireType] => delete [id] => 77 ) no error
And two others:
2022-01-21 12:35:17 741 -> NO PAYLOAD ON SAVE_POST
2022-01-21 12:34:01 741 -> PROCESSED delete Array ( [expireType] => delete [category] => [categoryTaxonomy] => [enabled] => 1 )
2022-01-21 12:33:59 741 -> SCHEDULED at Fri, 21 Jan 2022 12:32:00 -0500 (1642786320) with options Array ( [expireType] => delete [id] => 741 ) no error
2022-01-21 09:45:33 21220 -> NO PAYLOAD ON SAVE_POST
2022-01-21 09:44:43 21215 -> PROCESSED delete Array ( [expireType] => delete [category] => [categoryTaxonomy] => [enabled] => 1 )
2022-01-21 09:44:42 21215 -> SCHEDULED at Fri, 21 Jan 2022 09:32:00 -0500 (1642775520) with options Array ( [expireType] => delete [id] => 21215 ) no error
-
This reply was modified 4 years, 4 months ago by
Matt.
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
The two posts with the issue have “_expiration-date-status” == “saved” (and no other values).
The one I checked that didn’t have the issue does not have any metadata with ‘expiration’ in the name.
-
This reply was modified 4 years, 4 months ago by
Matt.
-
This reply was modified 4 years, 4 months ago by
Matt.
@andergmartins I don’t have permissions beyond the WP dashboard (content editing) and can’t retrieve the meta you requested. Sorry.
-
This reply was modified 4 years, 4 months ago by
jkorte.
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 update to version 2.7.2 which should fix this issue.
If it doesn’t fix this, please start a new thread with these 3 details:
1. Use a plugin like this to rollback to an earlier version: https://ww.wp.xz.cn/plugins/wp-rollback/. What specific versions do work correctly?
2. Disable other plugins one-by-one. Is there a plugin conflict here?
3. Share a screenshot of both your “Defaults” and your “Post Type” settings.`
The correct version is live here on ww.wp.xz.cn.