Timeline for Run a cron job (or similar) in the background of WP after post update/create
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot | replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/ | |
| Feb 17, 2012 at 16:33 | comment | added | turbonerd | Thanks Brian. Site gets enough traffic (30,000 unique visitors/week) so I think we'll be OK in those terms. The script isn't absolutely massive and there'll very rarely be more than one post at a time updated. | |
| Feb 17, 2012 at 16:29 | history | edited | Brian Fegter | CC BY-SA 3.0 | added 724 characters in body |
| Feb 17, 2012 at 16:22 | comment | added | Brian Fegter | Well, it's a psuedo-cron which depends on people visiting your site. It could create a performance issue for the unlucky user who hits your site when it's time to run the wp-cron. The more reliable approach to make sure the cron runs at scheduled intervals is to use crontab. You can see the wp-cron functions here: codex.wordpress.org/Category:WP-Cron_Functions | |
| Feb 17, 2012 at 16:15 | comment | added | turbonerd | Hi Brian. I was under the impression that WP had built-in features for setting up cron jobs? | |
| Feb 17, 2012 at 16:12 | history | answered | Brian Fegter | CC BY-SA 3.0 |