Cron events stop working after PHP 8.0 update

[domagron]

Hello,

I noticed that all wordpress cron events cease ruining upon migrating to PHP 8.0. When I change back to 7.4 the crdo events resume.

[peterwilsoncc]

Hi @domagron and welcome to trac!

Are you able to check your PHP logs for any errors and provide a stack trace?

WordPress has made a number of improvements for PHP 8+ recently see the keyword, especially for potential fatal errors.

A stack trace will help determine if the issue is within WordPress or a plugin that is incompatible with PHP 8+

[domagron]

The latest entry in the error log is from several weeks ago before the upgrade to 8.0. I will try deactivating plugin that use the cron one by one and manually run cron to see if it is plugin related.

[domagron]

Apologies. I was looking at the wrong server. Here is the error log

​https://1drv.ms/u/s!Asw7ieIRufLVgoJj56XV0WtN2EUEVg?e=oGbkru

[hellofromTonya]

Replying to domagron:

The latest entry in the error log is from several weeks ago before the upgrade to 8.0. I will try deactivating plugin that use the cron one by one and manually run cron to see if it is plugin related.

@domagron after deactivating the plugins, did the issue still happen? If yes, were you able to identify which plugin caused it?

[hellofromTonya]

Reviewed this ticket to determine if it is an incompatibility with PHP 8.0 and should be listed in the known incompatibilities for WP 6.3.

Findings: no, with the information at this time. This ticket is still being investigated to determine if it is a plugin that is incompatible with PHP 8+ or something in Core. Until determined to be a Core issue, the php-compatibility focus should not be added to the ticket.

Ticket changes:

• Removed needs-patch keyword. The ticket needs investigation first to determine if changes are needed in Core.
• Changed php8 to php80 to denote PHP 8.0 is the version that increased the error severity.

[johnbillion]

I'm going to close this ticket off as there's been no further feedback in two years. The log from @domagron is no longer available but it's quite likely the issue was caused by a plugin incompatibility with PHP 8 rather than anything specific in WordPress.

The majority of WordPress sites run on PHP > 8 now.

Thanks!