Geeklog Forums

I recently upgraded from GL 1.3.6 to 1.3.7, and I can't get the daily e-mail digest to work. I had it working in 1.3.6 as far as I can tell (I selected the digest for my Admin account for a couple of days, then deselected it once I confirmed that it was working). After installing 1.3.7 I selected it again for my Admin account, but it doesn't work. I edited the Include line in emailgeeklogstories to point to lib-common.php (despite the warning not to edit anything in the file), because that was what I needed to do in 1.3.6 to get it to work. What else should I check?

---

Kevin Horton

"It doesn't work" means that you get no emails, I assume? Do you have any new stories that have been added since it ran for the last time? When you disabled it, did you leave the cronjob running? If so, make sure you have new stories that were posted after the cronjob ran. You could also try running the script manually: Remove the first line (so that it starts with <?php ..., copy it into your document root and rename it to something that ends in .php. Then just type the URL into your browser. Good point about that note saying you shouldn't change anything in that file - of course you should change the include statement ... bye, Dirk

Thanks for the help Dirk. I ran the script manually and it worked (i.e. I got an e-mail - with several days worth of stories). Judging by the number of days of stories in the e-mail, this thing has been broken since before the upgrade to GL 1.3.7. I checked the cron job and it is still there, but I am now suspicious about the format of the entry. Should there be a "." ahead of the path to emailgeeklogstories (as if I was running the script from a shell), or should the path simply start with a "/"?---Kevin

---

Kevin Horton

If in doubt, I would use the absolute path, i.e. one starting with a / bye, Dirk

Hmm - does the emailgeeklogstories file need to be executable in order for crontab to run it? I tried making it executable - maybe that will help. We'll see tomorrow morning whether it has worked or not. If I can't sort it out I'll try using the cron on my local machine use lynx to hit the manual script every night.---Kevin

---

Kevin Horton

Yes, scripts must be executable to be executed by cron.

It seems that at some point the permissions of emailgeeklogstories had gotten changed so that the file was not executable. I made the file executable yesterday, and the digest was in my in-box this morning. I guess I should have known the file needed to be executable, but I'm pretty new to unix, and I suspect that many GL users are not true unix geeks. I think it would be useful to add two comment in emailgeeklogstories: 1. the path in the include line must be edited. 2. the file must have execute permissions set.---Kevin

---

Kevin Horton