#10200 closed defect (bug) (wontfix)
Cron not running
| Reported by: | firmdot | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Cron API | Version: | 2.8 |
| Severity: | normal | Keywords: | cron, schedule |
| Cc: | Focuses: |
Description
Since upgrading to 2.7 and now 2.8 we're unable to schedule posts. The error is missed schedule.
There are a number of people having this issue too, check page 3 for the most recent reports:
Change History (7)
#2
@
17 years ago
This is maybe a result of options cache stomping on each other.
In my debugging, I've noticed that options cache (cron) is seriously out of sync with the corresponding db records, especially when the user shedules multiple future posts within a few minutes. But it does seem to be caused by some changes in 2.8, because I saw this issue resurfaced again in the past several days.
#4
in reply to: ↑ 1
@
17 years ago
- Cc added
Replying to azaozz:
There are some changes to wp-cron in 2.8, see [10521]. Use the native cron if available or try adding
define('ALTERNATE_WP_CRON', true);to wp-config.php.
While adding that to my config file did work, it seems to create some funny links. I'm guessing this works by occasionally appending '?doing_wp_cron' to the URL. I've seen a few visitors to my site create links they've seen with that appended to the URL since making that change. And I'm seeing some of those URLs get indexed in Google that way:
http://www.google.com/search?q=inurl:%3Fdoing_wp_cron
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
There are some changes to wp-cron in 2.8, see [10521]. Use the native cron if available or try adding
define('ALTERNATE_WP_CRON', true);to wp-config.php.