Hi @oliverschmidt
I don’t think this is a problem. I have the same warning on my website and it works like a charm.
Maybe this is just a display issue.
Nevertheless I have opened an issue for this. Hopefully one of the devs can shed some light on this for us why it happens:
https://github.com/pluginkollektiv/statify/issues/184
Maybe because we add this in a private function?
All the best
Torsten
Hi,
@zodiac1978 is right, it only a UI issue here, functionality is given.
Statify only registers the actual cron action during cron execution. This has been the case since at least 1.4.0 when the project was ported to GitHub, so I can only guess the reason.
When you access the WP Control interface, you’re in a backend/admin request-cycle, not in a cron-cycle, so no action is registered and WP Control can’t see it. As soon as you click “run now” or whenever the a real cron task is running, Statify registers the action method and it gets executed when necessary.
Cheers,
Stefan
Hi Stefan,
Thanks for the very detailed – and helpful – explanation 🙂
Regards,
Oliver