Hi everybody,
I've been having some trouble with publish_another() in a way that
reminds me strongly of this thread:
http://www.gossamer-threads.com/lists/bricolage/users/39682
Here's how to reproduce my problem:
1. User schedules a publish of a story.
2. bric_queued executes the publish.
3. publish_another() jobs that SHOULD be scheduled in step 2 do not
appear in the job queue.
4. publishing the same story by mod_perl ("now" rather than scheduled,
or via bric_soap) DOES add the expected jobs to the queue.
The nutty thing is that if you repeat steps 1-3, and then have
bric_queued publish something whose template manually calls
flush_another_queue(), all the expected jobs get magically scheduled.
The problem is that if bric_queued handles the initial publish, the
another_queue only gets flushed if you intervene manually.
Obviously this is connected to the
one-burner-doesn't-know-enough-about-the-other-one issue. I see how
Nick's fix can help, but I don't see an easy way to avoid manually
flushing the queue. Can anybody suggest anything?
Thanks so much,
Bret
--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret@pectopah.com
www.pectopah.com
I've been having some trouble with publish_another() in a way that
reminds me strongly of this thread:
http://www.gossamer-threads.com/lists/bricolage/users/39682
Here's how to reproduce my problem:
1. User schedules a publish of a story.
2. bric_queued executes the publish.
3. publish_another() jobs that SHOULD be scheduled in step 2 do not
appear in the job queue.
4. publishing the same story by mod_perl ("now" rather than scheduled,
or via bric_soap) DOES add the expected jobs to the queue.
The nutty thing is that if you repeat steps 1-3, and then have
bric_queued publish something whose template manually calls
flush_another_queue(), all the expected jobs get magically scheduled.
The problem is that if bric_queued handles the initial publish, the
another_queue only gets flushed if you intervene manually.
Obviously this is connected to the
one-burner-doesn't-know-enough-about-the-other-one issue. I see how
Nick's fix can help, but I don't see an easy way to avoid manually
flushing the queue. Can anybody suggest anything?
Thanks so much,
Bret
--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret@pectopah.com
www.pectopah.com