| Project: | Elysia Cron |
| Version: | 7.x-2.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
A fresh download of elysia_cron onto a Drupal 7.10 site.
file: elysia_cron.module
<?php
if ($manual_run) {
if ($result) {
drupal_set_message(t('Cron ran successfully'));
}
else {
drupal_set_message(t('Cron run failed, disabled or nothing to do'));
}
drupal_goto(_dcf_internal_path('admin/reports/status')); <- this is the problem
}
exit();
?>Somehow, Elysia gets stuck - I believe because $result is false, and it winds up trying to send the user to admin/reports/status over and over - because it has a check for "admin" as the path, if so, it tries to manually run.
I was able to fix it, from what it looks like by changing two things:
1) This variable was the culprit I believe, and I am not sure how it got defined. Might have been another user in the system trying to kill off the module from misbehaving.drush variable-delete elysia_cron_disabled
2) disable the "poormanscron" concept (which should be default in my opinion when installing Elysia!)drush vset cron_safe_threshold 0
Either way there should be something a little more robust around that. Sorry if I can't give you the exact conditions to reproduce, that's the best information I could document. Looks like there might just be a little bit of logic around that behavior in elysia_cron_cron()