09-24-2018, 05:41 PM
This is what I do:
- open the command line and go to the coreBOS directory
- open config.inc.php or config-dev.inc.php and add: error_reporting(E_ALL);ini_set('display_errors',1);
- reset the scheduled task in Settings
- manually launch the cron in question: php vtigercron.php ScheduleReports
that usually shows the error on screen and gives you the first steps to start debugging
When you have to launch the cron repeatedly I usually reduce the time directly in vtiger_crontask table
When it gets REALLY complicated you can activate the BACKGROUND log in log4php as that log gives you cron/workflow detailed information
- open the command line and go to the coreBOS directory
- open config.inc.php or config-dev.inc.php and add: error_reporting(E_ALL);ini_set('display_errors',1);
- reset the scheduled task in Settings
- manually launch the cron in question: php vtigercron.php ScheduleReports
that usually shows the error on screen and gives you the first steps to start debugging
When you have to launch the cron repeatedly I usually reduce the time directly in vtiger_crontask table
When it gets REALLY complicated you can activate the BACKGROUND log in log4php as that log gives you cron/workflow detailed information
Joe
TSolucio
TSolucio