There are so many things I don't understand.
Lennart Regebro
it, but I don't get it. For example:
How is the schedulers actually supposed to work?
What is a manual scheduler?
Why can I select "no value" for a scheduler, and what happens then?
I hoped most of these things would become clear, but they didn't. I
still don't get it.
Currently I try to send a preview, but it just says that nothing was
sent, "0 message(s) queued." If something is wrong, can I get a
frigging error message, please?
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
Daniel Nouri
> Can somebody explain Singing & Dancing to me. I know I have extended
> it, but I don't get it. For example:
>
> How is the schedulers actually supposed to work?
> What is a manual scheduler?
> Why can I select "no value" for a scheduler, and what happens then?
>
> I hoped most of these things would become clear, but they didn't. I
> still don't get it.
IScheduler has a "tick" that's called periodically. "tick" calls
"trigger", which is also in IScheduler, when it's time to send out
messages. E.g. every week "tick" will find out that the time has
come, call "trigger" and set the "triggered_last" time. What's
triggered is always the IMessageAssemble component that does the hard
job.
A manual scheduler never calls its own "trigger" method. Thus, it can
only be manually triggered, in the sense that someone calls "trigger"
directly. This is possible through the scheduler UI: You can trigger
any scheduler manually, regardless of when it's programmed to go off
the next time.
> Currently I try to send a preview, but it just says that nothing was
> sent, "0 message(s) queued." If something is wrong, can I get a
> frigging error message, please?
Errors are usually logged. What's happening here is probably that
your newsletter didn't have any contents, and thus wasn't sent out.
Which you normally want to happen if e.g. no news items were published
in the current week.
There's two other things that play a role here: 1) Collector items can
be "significant" or not. If a newsletter has one significant item,
it'll be sent out. 2) Each subscriber object holds a "cue", which,
per default, holds the time of the last send-out. If your news items
are older than that cue, you won't receive them. However, the preview
doesn't use a cue as far as I know. And it's also optional and you
can configure the MessageAssemble implementation to not use them.
I hope this makes things a little clearer.
Daniel
Lennart Regebro
A little bit.
One problem I had is that if you type in another mail address than a
subscriber the preview will not be sent, without error message. That
was confusing. But I can send things now, although I'm not entirely
sure why news items never sent and less than a week old doesn't show
up.
Could the cue setting be set even if you are not a subscriber and even
in previews?
Daniel Nouri
Bummer. I was aiming for more.
> One problem I had is that if you type in another mail address than a
> subscriber the preview will not be sent, without error message. That
> was confusing. But I can send things now, although I'm not entirely
> sure why news items never sent and less than a week old doesn't show
> up.
>
> Could the cue setting be set even if you are not a subscriber and even
> in previews?
There's no cue without an existing subscriber, IIRC. I suggest you
try and debug a bit around where MessageAssemble looks at the
"use_cue" variable, and find out what's going on. All of this has
pretty good test coverage, even though it's certainly complicated.
Daniel