Cronjobs Not Set
I've entered the cronjob commands for the Links and Twitter modules and I'm still getting a "Not all cronjobs are set" error message. I don't have the same error message with Google Analytics. This is what I have set:
Current Cron Jobs Minute Hour Day Month Weekday Command Actions
*
* *
* `* http://fork.abateofstny.org/backend/cronjob.php?module=core&action=processqueuedhooks
*
* *
* `* http://fork.abateofstny.org/backend/cronjob.php?module=core&action=sendqueuedemails
33 0 *
* `* php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=analytics action=getdata
34 0 *
* `* php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=analytics action=gettraffic_sources
0 0 *
* 0 php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=links action=checklinks
24 *
* *
* php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=twitter action=gettweets
Can anybody give me some advice?
Thanks!
I've entered the cronjob commands for the Links and Twitter modules and I'm still getting a "Not all cronjobs are set" error message. I don't have the same error message with Google Analytics. This is what I have set:
Current Cron Jobs Minute Hour Day Month Weekday Command Actions
*
* *
* `* http://fork.abateofstny.org/backend/cronjob.php?module=core&action=processqueuedhooks
*
* *
* `* http://fork.abateofstny.org/backend/cronjob.php?module=core&action=sendqueuedemails
33 0 *
* `* php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=analytics action=getdata
34 0 *
* `* php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=analytics action=gettraffic_sources
0 0 *
* 0 php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=links action=checklinks
24 *
* *
* php /home/abateo5/publichtml/fork/app/../backend/cronjob.php module=twitter action=gettweets
Can anybody give me some advice?
Thanks!
Sorry for posting twice, but I can't seem to get the commands to display properly for review.
What Fork CMS version are you using?
In the latest versions there's a bug like that. I've got that problem also. CAn you file a github issue for that?