POPfetcher and cronjob scheduler

[sorensilk]

OK, I have read a ton of threads on this and still can't quite get it to work. I have the POP fetcher part working great, it pulls my emails and posts them when I use the manual internal popfetcher.

I'm trying to get the cronjob scheduler to do this for me though. Both plugins are installed and I *think* I'm just messing up on the part of popfetcher with the External Launch Name. What exactly do I need in there? I have the Execute set to 5 min for now, the type is set to external, and I've tried all kinds of things in the External Launch Name box.

Also, once I set that, do I need to to set anything else on my actual site or on the cronjob scheduler plugin?

Thanks for any help.

[garvinhicking]

Hi!

I suppose you are using Popfetcher version 1.16 or 1.17, right? And you set the cronjob execution time within the configuration of the popfetcher plugin.

When you use the cronjob plugin it actually does not matter what you enter as external execution name.

Have you checked the cronjob plugin configuration? In it you should see a log of cronjob events, do you see something there?

Everything should be logged to a serendipity_cronjoblog database table...

Best regards,
Garvin

[sorensilk]

OK, I may have just been thinking about it wrong. So if I use the cronjob scheduler plugin I either have to leave it on visitor-based cronjobs and it will only run the cronjob and start popfetcher when my page is visited.

The other option would be to turn off visitor-based cronjobs and set "wget http://yourblog/index.php?serendipity[cronjob]=all" on the crontab of my own server.

Is that right?

[garvinhicking]

Hi!

OK, I may have just been thinking about it wrong. So if I use the cronjob scheduler plugin I either have to leave it on visitor-based cronjobs and it will only run the cronjob and start popfetcher when my page is visited.

That's true. Cronjobs can only be activated by visitors, or by some external script accessing your pages form a different server's cronjob!

There's no mean to make the cronjob plugin "run in the background"...

Best regards,
Garvin