Cron Job/Events with No Action

  • Resolved carmpocalypse

    (@carmpocalypse)


    2 years, 4 months ago

    Hello,

    There are 3 Cron Jobs with no actions associated with them. The hooks are tsf_sitemap_cron_hook_before, tsf_sitemap_cron_hook, and tsf_sitemap_cron_hook_after. Is it safe to delete these or do they serve a purpose even with no actions?

Viewing 3 replies - 1 through 3 (of 3 total)

  • Can I ask you why you want to delete them, please? Realistically, there is no measurable performance gain. The crons exists so you can hook your own actions, for example if you need to add custom pages.

    Is there something specific you want to achieve by removing the crons? Or you are just experimenting with things to gain some website speed performance?

    BTW thank you for taking the time to write TSF a nice review, much appreciated!

    Cheers, Pierre.

    Thread Starter carmpocalypse

    (@carmpocalypse)

    @lebaux

    Curious what they were for. If at some point I can use them to hook my own actions in there I will leave them. Thanks for the quick reply.

    Plugin Author Sybre Waaijer

    (@cybr)

    Hello! Here’s some dev-feedback.

    Those cron hooks get registered every time the sitemap needs updating; this is when you edit the settings, update or publish a post, change the permalinks, etc.

    After the cron-hooks fired, they are deleted: we use wp_schedule_single_event().

    You can disable this type of cron-based event at “SEO Settings > Sitemap Settings > Ping > Use cron for pinging?”. TSF will then fall back to pinging directly. Updating a post might take slightly longer, however.

    Pinging via cron or directly is done at most once per hour. TSF registers this timeout at the moment of pinging.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cron Job/Events with No Action’ is closed to new replies.