Skip to content

Commit

Permalink
More links.
Browse files Browse the repository at this point in the history
  • Loading branch information
johnbillion committed Mar 13, 2024
1 parent 7d97e01 commit a692093
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/docs/how-to-use.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ function my_function() {

## Add a new PHP cron event

[[See here for full information about creating PHP cron events]].
[See here for full information about creating PHP cron events](https://wp-crontrol.com/docs/php-cron-events).

## Pause cron events

Expand Down
2 changes: 1 addition & 1 deletion docs/help/problems-managing-events.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,4 @@ If you try to add, delete, or edit a cron event and the changes aren't saved, th
* Try again. Often the problem is sporadic and making the change a second time will work. For example this problem can occur if you make a change right at the time when a cron event is being run by WordPress.
* Ensure the event is not scheduled within 10 minutes of another event with the same hook. If the event is not a recurring event, WordPress core will block this "duplicate" event and the error message may not indicate this.
* Try deactivating any plugins that provide a persistent object cache, for example Redis or Memcached. This is not ideal of course, but it can help you get to the root of the problem.
* Read through the [[Cron events that have missed their schedule]] page. Much of the information there applies to creating and editing events too.
* Read through the [Cron events that have missed their schedule](https://wp-crontrol.com/help/missed-cron-events/) page. Much of the information there applies to creating and editing events too.
2 changes: 1 addition & 1 deletion docs/help/wp-cron-lock-timeout.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,6 @@ You may not need to fix anything, but you should remain aware of the potential l

## How do I fix this?

Firstly, take a look at the [[Cron events that have missed their schedule]] page, there's lots of useful information on there.
Firstly, take a look at the [Cron events that have missed their schedule](https://wp-crontrol.com/help/missed-cron-events/) page, there's lots of useful information on there.

Secondly, you should either adjust the interval at which the cron events run so they run less frequently, or decrease the value of `WP_CRON_LOCK_TIMEOUT`. The effects of changing this constant are a bit beyond the scope of this document but I'll try to add some more info here in the future.
2 changes: 1 addition & 1 deletion readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,7 @@ The next step is to write your function. Here's a simple example:

In the Tools → Cron Events admin panel, click on "Add New". In the form that appears, select "PHP Cron Event" and enter the schedule and next run time. The event schedule is how often your event will be executed. If you don't see a good interval, then add one in the Settings → Cron Schedules admin panel. In the "Hook code" area, enter the PHP code that should be run when your cron event is executed. You don't need to provide the PHP opening tag (`<?php`).

[You can read all about the features and security of PHP cron events on the WP Crontrol website](https://wp-crontrol.com/docs/php-cron-events).
[You can read all about the features and security of PHP cron events on the WP Crontrol website](https://wp-crontrol.com/docs/php-cron-events/).

### Which users can manage cron events and schedules?

Expand Down

0 comments on commit a692093

Please sign in to comment.