• Resolved tm110821

    (@tm110821)


    We have a daily podcast that is supposed to expire (delete) the old podcast at 12:59 and then start the new one at 00:00 midnight. Since the last couple updates it has been sporadic at best. The old one may expire and then the new one doesn’t become published even though it is scheduled to do so. Or the new one publishes and the old one doesn’t delete so it plays after the new one.Here is the latest debugging log. Thanks in advance for any help.

    2021-11-08 07:12:30
    42248 -> NO PAYLOAD ON SAVE_POST
    2021-11-08 06:38:34
    42251 -> SCHEDULED at Tue, 09 Nov 2021 06:59:00 -0700 (1636441140) with options Array ( [expireType] => delete [id] => 42251 ) no error
    2021-11-08 01:57:28
    42251 -> SCHEDULED at Tue, 09 Nov 2021 06:59:00 -0700 (1636441140) with options Array ( [expireType] => delete [id] => 42251 ) no error
    2021-11-08 01:42:34
    42251 -> NO PAYLOAD ON SAVE_POST
    2021-11-07 19:45:54
    42248 -> SCHEDULED at Mon, 08 Nov 2021 06:59:00 -0700 (1636354740) with options Array ( [expireType] => delete [id] => 42248 ) no error
    2021-11-07 10:23:26
    40476 -> PROCESSED draft Array ( [expireType] => draft [category] => [categoryTaxonomy] => )
    2021-11-06 06:07:18
    42248 -> SCHEDULED at Mon, 08 Nov 2021 05:59:00 -0700 (1636351140) with options Array ( [expireType] => delete [id] => 42248 ) no error
    2021-11-06 06:04:55
    42248 -> SCHEDULED at Mon, 08 Nov 2021 05:59:00 -0700 (1636351140) with options Array ( [expireType] => delete [id] => 42248 ) no error
    2021-11-06 05:59:24
    42239 -> PROCESSED delete Array ( [expireType] => delete [category] => [categoryTaxonomy] => )
    2021-11-06 02:31:09
    42239 -> SCHEDULED at Sat, 06 Nov 2021 05:59:00 -0600 (1636178340) with options Array ( [expireType] => delete [id] => 42239 ) no error
    2021-11-06 02:30:14
    42248 -> SCHEDULED at Mon, 08 Nov 2021 05:59:00 -0700 (1636351140) with options Array ( [expireType] => delete [id] => 42248 ) no error
    2021-11-06 01:41:06
    42248 -> SCHEDULED at Mon, 08 Nov 2021 06:59:00 -0700 (1636354740) with options Array ( [expireType] => delete [id] => 42248 ) no error
    2021-11-06 01:39:54
    42248 -> SCHEDULED at Mon, 08 Nov 2021 06:59:00 -0700 (1636354740) with options Array ( [expireType] => delete [id] => 42248 ) no error
    2021-11-06 01:25:53
    42248 -> NO PAYLOAD ON SAVE_POST
    2021-11-05 15:26:01
    42239 -> SCHEDULED at Sat, 06 Nov 2021 05:59:00 -0600 (1636178340) with options Array ( [expireType] => delete [id] => 42239 ) no error
    2021-11-05 09:51:47
    42239 -> SCHEDULED at Sat, 06 Nov 2021 05:59:00 -0600 (1636178340) with options Array ( [expireType] => delete [id] => 42239 ) no error

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author andergmartins

    (@andergmartins)

    Hi @tm110821

    Please, could you let us know if you have set the constant DISABLE_WP_CRON?
    Do you see the cron events on the plugin’s settings page?

    Please, check: https://publishpress.com/knowledge-base/technical-details/

    If you don’t have been using DISABLE_WP_CRON, please could you follow this tutorial for disabling WP-Cron?

    https://kinsta.com/knowledgebase/disable-wp-cron/

    Thanks,

    Anderson

    Thread Starter tm110821

    (@tm110821)

    I followed the instructions for Disable CRON, adding define(‘DISABLE_WP_CRON’, true);
    to the wp-config file right above That’s all line
    and it then threw a fatal error in the post Expirator plugin. So I put the wp-config back to what it was
    DISABLE_WP_CRON WP cron status Enabled

    Another weird thing is that if I deactivate and then reactivate the Post Expirator plugin it will show the CRON event in PE diagnostics tab and also in the CRON line of WordFence diagnostics tools tab. If I don’t do that it doesn’t show it.

    Another thing is that the issues only seem to affect podcast files as far as posts not publishing as scheduled. A regular post will publish.

    • This reply was modified 4 years, 7 months ago by tm110821.
    Plugin Author Steve Burge

    (@stevejburge)

    Hi @tm110821

    Can you share what the fatal error message was, please?

    Thread Starter tm110821

    (@tm110821)

    Hello Steve,

    I had received an automatic error email as shown below right after I added the CRON fix in our config file. Note: the issue with the new daily podcast not publishing didn’t occur last night. Everything went as it should. The only difference I know of was an update to Staff List Pro plugin. This all may be related to that plugin causing a conflict somehow. I am hoping it all goes well again tonight with the daily podcast changeover.

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, Post Expirator.

    WordPress version 5.8.2
    Current plugin: Post Expirator (version 2.6.2)
    PHP version 7.4.19

    An error of type E_COMPILE_ERROR was caused in line 297 of the file /app/plugins/post-expirator/classes/Display.class.php. Error message: require_once(): Failed opening required ‘/app/plugins/post-expirator/classes/post-expirator-debug.php’ (include_path=’.:/usr/share/pear:/usr/share/php’)

    Thread Starter tm110821

    (@tm110821)

    HEllo Steve,

    Last night I could see where the daily podcast cron job wasn’t scheduled to publish. The expire was showing but not the future publish.I deactivated and then reactivated the Staff List Pro plugin and it appeared correctly The podcast then published correctly at the scheduled time. It appears that there is a definite issue with Staff List Pro. I am reaching out to them again.

    Thanks

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks @tm110821

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Posts not expiring correctly’ is closed to new replies.