Question about triggered republishing

Hi everybody. This question is about a 1.8.6 Bricolage
installation.

Many of the templates on this installation cause the home
page to be 
republished.

Today, one of the editors (let's call him "Bill")
was working on an 
update to the home page itself. This update isn't scheduled
to go live 
until tomorrow.

Bill had the home page checked out. It was on a publish
desk.

Then Bill published another document. This caused the home
page to be 
published, which pushed Bill's in-progress content to the
live site a 
day early.

Bill had expected that the home page would not be published
because he 
had it checked out. I'm wondering if the first issue was
that it was 
Bill himself who had it checked out, and if the second was
that the home 
page was on a publish desk.

We rolled the home page back, so no major problem there. But
can 
somebody tell me whether this is expected behaviour for
1.8.6?


Thanks so much,

Bret


P.S. One other interesting thing is that after the home page
was 
republished, it was removed from workflow, but it was still
checked out 
to Bill. When he viewed his workspace he got an error
message, but was 
able to check it into a desk at that point. Is this expected
behaviour?







-- 
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bretpectopah.com
www.pectopah.com

Actually, I was reading the log wrong. The home page was NOT
on a 
publish desk at the time.

Thanks again,

Bret

Bret Dawson wrote:
> Hi everybody. This question is about a 1.8.6 Bricolage
installation.
> 
> Many of the templates on this installation cause the
home page to be 
> republished.
> 
> Today, one of the editors (let's call him
"Bill") was working on an 
> update to the home page itself. This update isn't
scheduled to go live 
> until tomorrow.
> 
> Bill had the home page checked out. It was on a publish
desk.
> 
> Then Bill published another document. This caused the
home page to be 
> published, which pushed Bill's in-progress content to
the live site a 
> day early.
> 
> Bill had expected that the home page would not be
published because he 
> had it checked out. I'm wondering if the first issue
was that it was 
> Bill himself who had it checked out, and if the second
was that the home 
> page was on a publish desk.
> 
> We rolled the home page back, so no major problem
there. But can 
> somebody tell me whether this is expected behaviour for
1.8.6?
> 
> 
> Thanks so much,
> 
> Bret
> 
> 
> P.S. One other interesting thing is that after the home
page was 
> republished, it was removed from workflow, but it was
still checked out 
> to Bill. When he viewed his workspace he got an error
message, but was 
> able to check it into a desk at that point. Is this
expected behaviour?
> 
> 
> 
> 
> 
> 
> 


-- 
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bretpectopah.com
www.pectopah.com

On Sep 28, 2006, at 11:01, Bret Dawson wrote:

> Then Bill published another document. This caused the
home page to  
> be published, which pushed Bill's in-progress content
to the live  
> site a day early.

When your templates look up stories via the API, always pass
 
'published_version => 1' to list() or lookup(). This
should work  
properly for 1.8.4 and later. You then pass the returned
story or  
stories to publish_another(), and the published version will
be  
republished, rather than thew current version (which may, as
you've  
noticed, be checked out to someone).

> Bill had expected that the home page would not be
published because  
> he had it checked out. I'm wondering if the first issue
was that it  
> was Bill himself who had it checked out, and if the
second was that  
> the home page was on a publish desk.
>
> We rolled the home page back, so no major problem
there. But can  
> somebody tell me whether this is expected behaviour for
1.8.6?

It is.

> P.S. One other interesting thing is that after the home
page was  
> republished, it was removed from workflow, but it was
still checked  
> out to Bill. When he viewed his workspace he got an
error message,  
> but was able to check it into a desk at that point. Is
this  
> expected behaviour?

Yes, but obviously it's best avoided by using the
published_version  
parameter.

Best,

David

Ah. Thanks so much for this.

Cheers,

Bret

David E. Wheeler wrote:

> When your templates look up stories via the API, always
pass  
> 'published_version => 1' to list() or lookup(). This
should work  
> properly for 1.8.4 and later. You then pass the
returned story or  
> stories to publish_another(), and the published version
will be  
> republished, rather than thew current version (which
may, as you've  
> noticed, be checked out to someone).
> 
>> Bill had expected that the home page would not be
published because  
>> he had it checked out. I'm wondering if the first
issue was that it  
>> was Bill himself who had it checked out, and if the
second was that  
>> the home page was on a publish desk.
>>
>> We rolled the home page back, so no major problem
there. But can  
>> somebody tell me whether this is expected behaviour
for 1.8.6?
> 
> 
> It is.
> 
>> P.S. One other interesting thing is that after the
home page was  
>> republished, it was removed from workflow, but it
was still checked  
>> out to Bill. When he viewed his workspace he got an
error message,  
>> but was able to check it into a desk at that point.
Is this  expected 
>> behaviour?
> 
> 
> Yes, but obviously it's best avoided by using the
published_version  
> parameter.
> 
> Best,
> 
> David
> 
> 
> 


-- 
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bretpectopah.com
www.pectopah.com