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

List:       bricolage-general
Subject:    Re: [Bricolage-General] Shelving media that shouldn't be published (and preventing autopublishing)
From:       David Wheeler <david () kineticode ! com>
Date:       2004-01-31 19:51:50
Message-ID: E8F2C5C7-5426-11D8-BE21-000A95972D84 () kineticode ! com
[Download RAW message or body]

On Jan 31, 2004, at 11:44 AM, Patrick J. Walsh wrote:

> 	1.6.8.  It didn't occur to me that this shouldn't happen.  Does it
> make a difference that it's being autopublished as a related story 
> instead
> of being published directly?

No.

> 	It's a custom story with its own template that has just this:
>
>> <%once>;
>> if ($burner->get_mode == PUBLISH_MODE) {
>>    $m->clear_buffer;
>>    $m->abort;
>> }
>> </%once>
>
> 	In the related_story temlate if a story of this type is referenced
> i just grabs the data from the data field and outputs it without ever
> calling display_elements or anything like that.

Yes, it should just work.

> 	The story being referenced is just sitting on the Edit desk and
> has never been published.  I'm not even sure it should be 
> autopublished.
> I didn't think that happened with stories.  Anyway, the error comes up
> when publishing the story that has it listed as related...

If it has never been published, it shouldn't generate the error, 
because the template hasn't been executed to abort.

David



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general
[prev in list] [next in list] [prev in thread] [next in thread]