yannunil

Ok we completely removed the Apache rules (Location directives) related to authentication (not only the Require attributes as we tried before) and it works, post are expiring.

It seems that WP CRON uses network connections to trigger the jobs.

So in case someone has the same problem in the future, here is a rule to exclude the wp-cron from the authentication (for site mysite):

<Location ~ "/mysite/(wp-cron.php)"> 
     AuthType None
     Satisfy Any
     Allow from all
     Require all granted
</Location>

Regards.

Hi,

I’m back, sorry for the late reply.

@soumilroy Thank you for commenting. Unfortunately it seems to be a different problem in my case. I only have 18 jobs in the wp_options table and not all are related to Post Expirator (anyway, your query is a little bit radical as it deletes all crons from the DB, not only those related to Post expirator).

@axelseaa Thank you, the specified diagnostics logs were extracted from a test with a brand new post.

The only difference with other sites in my installation is that this site is protected (Shibboleth authentication rule defined at Apache level), but removing the rule seems not to help.

I will try to disable the built-in cron and setup a new cron job, without convictions…