Opened 7 years ago
Last modified 7 months ago
#43801 new enhancement
Need better documentation to show importance of checking for args while using wp_schedule_event and wp_next_scheduled
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | Cron API | Keywords: | good-first-bug has-patch |
Focuses: | docs | Cc: |
Description
While the user notes https://developer.wordpress.org/reference/functions/wp_next_scheduled/#user-contributed-notes do relay the importance. I believe it is important that the documentation also be more clear about the issue.
When coded incorrectly something like
function schedule_my_event(){ if ( ! wp_next_scheduled( 'myevent' ) ) { // This will always be false wp_schedule_event( time(), 'daily', 'myevent', array( false ) ); } } add_action('init','schedule_my_event');
It's potentially disastrous for a site. The cron value in the options would keep on increasing until the database could no longer withstand it.
So keeping that in mind I feel the documentation for both wp_next_scheduled and wp_schedule_event should highlight this point more.
Attachments (1)
Change History (5)
#2
@
4 years ago
- Keywords needs-patch good-first-bug added
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
This ticket was mentioned in PR #7055 on WordPress/wordpress-develop by @roshniahuja14.
7 months ago
#4
Trac ticket: [](https://core.trac.wordpress.org/ticket/43801)
Note: See
TracTickets for help on using
tickets.
adding missing documentation text for
wp_schedule_event
andwp_next_scheduled
functions