security updates of unpatched modules
This commit is contained in:
@@ -126,7 +126,7 @@ You can use the "hook_cron_alter" function to edit cronapi data of other
|
||||
modules.
|
||||
|
||||
Example:
|
||||
function module_cron_alter($data) {
|
||||
function module_cron_alter(&$data) {
|
||||
$data['key']['rule'] = '0 */6 * * *';
|
||||
}
|
||||
|
||||
@@ -182,6 +182,19 @@ function phptemplate_elysia_cron_description($job) {
|
||||
Note: module default theme_elysia_cron_description($job) already contains
|
||||
some common tasks descriptions.
|
||||
|
||||
-----------------------------------------------------------------------------
|
||||
DISABLE CRON JOBS VIA settings.php FILE
|
||||
-----------------------------------------------------------------------------
|
||||
If you have some instances for the project you can want to disable some cron
|
||||
jobs on different instances. For example you don't want to execute PROD cron
|
||||
jobs on DEV instance. There is no need to make it via interface or via SQL
|
||||
query. You can define variable for each cron job to manage it state. For more
|
||||
information please look at `_elysia_cron_is_job_disabled` and `_ec_get_name`
|
||||
functions.
|
||||
|
||||
For example, if you have cron job with name googleanalytics_cron, you can
|
||||
add this string to your settings.php file:
|
||||
$conf['ec_googleanalytics_cron_d'] = TRUE;
|
||||
|
||||
-----------------------------------------------------------------------------
|
||||
OLD 1.x MODULE API (OBSOLETE)
|
||||
|
||||
Reference in New Issue
Block a user