Thank you for bringing this to our attention.
We’ve noted the issue and are currently investigating it. We’ll share our findings with you as soon as the investigation is complete.
Thanks for your patience.
Currently, WordPress uses arrays for cron event arguments. Upon investigation, we confirmed that the issue was caused by a legacy cron event from an older version of Breeze still present in the database.
WP Crontrol has since released an update (v1.21.0) that prevents the fatal error and allows these events to be managed directly through its interface. To resolve the issue, please update WP Crontrol to the latest version and manually remove the legacy Breeze cron event from your Cron Events list. Alternatively, you can clear it via the command line using:
wp cron event delete breeze_clear_remote_gravatar --all
Additionally, we identified that the gravatar cron unschedule event still uses the outdated string argument. While this does not cause the WP Crontrol error, it may prevent the event from being unscheduled when the gravatar option is disabled.
