Make WordPress Core

Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#4388 closed enhancement (wontfix)

Configuration page for wp-cron jobs

Reported by: Otto42 Owned by:
Milestone: Priority: low
Severity: normal Version:
Component: Optimization Keywords: plugin-management cron
Focuses: Cc:


Add a configuration page (admin only) for the actions to be performed by wp-cron. This page will let users view these actions as well as remove them.

This is necessary because I've noticed some plugins ("Cronless Postie", for example) starting to use the wp-cron functions, but not removing their wp-cron jobs when the plugins are disabled. While this is a problem with these plugins, to be sure, there is currently no way to disable or remove a "rogue" wp-cron job that a plugin scheduled but never unscheduled.

In extreme cases, activating and deactivating a plugin repeatedly can cause multiple repeating jobs to be inserted into the wp-cron job list, causing excessive load when it tries to run these jobs multiple times. This can kill a site and use a lot of bandwidth for no reason that is obvious to the user or the host, making them blame Wordpress for "being slow" and such. Visibility of the wp-cron job actions would provide a way to fix this as well as point out the likely source of the bad plugin.

Change History (8)

#1 @JeremyVisser
13 years ago

Plugin material, IMO. In the same boat as the Role Manager plugin.

#2 @Otto42
13 years ago

Role Manager can't bring down your blog by lack of its presence. Unwittingly activating and deactivating a badly written plugin several times can run up your bandwidth bill and cause wp-cron to go nuts. Having a way to fix this should be in the core, IMO.

#3 @darkdragon
12 years ago

Dude! This would be awesome!

It shouldn't be that difficult, so I'll try to work on something basic sometime next week. If anything, I'll create it as a plugin with a patch for core.

#4 @darkdragon
12 years ago

  • Keywords plugin-management cron added

#5 @darkdragon
12 years ago

There is already a plugin for this.

#6 @darkdragon
12 years ago

  • Milestone changed from 2.5 to 2.6

#7 @pishmishy
12 years ago

  • Milestone 2.6 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I think this should remain plugin territory.

Badly written plugins can cause all sorts of problems and I'm not sure we should change the interface, to add something most users won't understand, to help solve just one of these problems.

My first bit of advice to people experiencing problems with WordPress is usually to disable every plugin and see what happens.

#8 @Otto42
12 years ago

The problem with this issues is that disabling the problematic plugins won't help. The damage has been done, the entries are in the cron jobs with no way to remove them.

While this has indeed been a big problem for some people, a few plugins have been made to deal with it since I created this ticket.

I refer people to WP-Crontrol: http://wordpress.org/extend/plugins/wp-crontrol/

Still, I think that WP could potentially be made smarter here and possibly deal with this situation automatically. However, a plugin is fine for now.

Note: See TracTickets for help on using tickets.