WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #49520


Ignore:
Timestamp:
02/27/2020 01:45:30 AM (11 months ago)
Author:
SergeyBiryukov
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #49520 – Description

    initial v1  
    88The latter specifically has long been responsible for the infamous "missed schedule" issue in WordPress - a critical functionality of publishing posts at a certain time being completely unreliable.
    99
    10 https://core.trac.wordpress.org/ticket/39924
    11 https://core.trac.wordpress.org/ticket/41965
    12 etc.
     10#39924, #41965, etc.
    1311
    1412https://github.com/humanmade/Cavalcade needed to be created to properly resolve this, but it's a 3rd party solution that isn't as trivial to set up as activating a plugin, and shouldn't be necessary in well-designed software. I see the cron problem as WordPress's biggest and most glaring flaw, and I'm sure many would agree.
     
    1614So, what's the solution? Can cron be migrated into its own wp_cron table and the related functions made to interact with the migrated data transparently to the user? I know it'd be a pretty big project, but it's one of those bandaids that just needs to be finally ripped off.
    1715
    18 https://core.trac.wordpress.org/ticket/15148 was closed as `wontfix`, but I hope the team can reconsider.
     16#15148 was closed as `wontfix`, but I hope the team can reconsider.
    1917
    2018Thank you.