#wordpress 2020-11-02
2020-11-02 UTC
[fluffy], [tantek], [Hideo_Minami], nickodd and [chrisbergr] joined the channel; nickodd left the channel
#
petermolnar beko: WordPress has a debug log option, plug turn error logging to debug level in PHP

#
petermolnar get one of them wordpress cron editor plugins, then deactivate the webmentions plugin, and activate it again

#
petermolnar see if anything happens with the cron list

#
petermolnar beko: that is not how WP works :).

#
petermolnar You have a trigger which is either a real crontab entry, or a web action, but that only triggers the internal wordpress cron main hook. The internal one has a list of tasks to execute

[grantcodes] joined the channel
#
[grantcodes] "Have you tried turning it off and on again?" never fails!

#
petermolnar if something goes wrong, these tasks get messed up, unregistered, registered too often, etc. If a plugin is reasonably well written, it'll de-register on deactivation and re-register on activation

#
petermolnar tihs is why it got fixed for you.

#
petermolnar the wp cron stack is a monster; when I made an alternative webmentions plugin I tried to make it completely asynchronous and I was messing a lot with the wp-cron options. It's BAD.

#
petermolnar [grantcodes]: these modern days of serverless systemless wordpressless blogging, one eventually needs to know _what_ to turn off and on again :D

[KevinMarks], jeremych_, [tantek], [Hideo_Minami], gRegorLove, [fluffy], [tonz], [jeremycherfas] and [schmarty] joined the channel