[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-devel
Subject:    Re: timing of setting stories to published
From:       "David E. Wheeler" <david () kineticode ! com>
Date:       2007-11-24 21:07:33
Message-ID: C151C7C6-9C33-4B38-91C5-CC5D0CEB3E33 () kineticode ! com
[Download RAW message or body]

On Nov 24, 2007, at 07:52, Beaudet, David P. wrote:

>> Yes, if you can roll it back, it can be set before. Although it kind
>> of doesn't make sense. If the version is currently being published
>> (and is being published for the first time), it's not really the
>> published version yet, is it?
>
> No, it's not technical published yet, but when publishing multiple  
> stories at the same time, say A and B, it makes sense for the  
> versions currently being published to be visible to each other as  
> the published version.  That way, I don't have to publish A, then  
> B, then A again in order for A to be as up-to-date as possible.

Oh, but with the patch you're using, that's the way it *should* be,  
no? Because publish_another() just schedules a job, and the job runs  
after the current nob is completed, no?

Best,

David
[prev in list] [next in list] [prev in thread] [next in thread]