how to file a feature request ticket?

Hi I just went to
>
>   http://bugs.bricolage.cc/

and am looking for a way to how  feature request ticket or
perhaps  
'add a request' in other parlance.

I only see a way to make a bug report, but no way to
indicate this is  
not a bug but a request. I've gone through the documentation
too.

thank you

Dawn

 
I think that after you fill out the "bug report",
you'll be able to categorize it as an enhancement request.

________________________________

From: Dawn Buie [mailto:dawnthetyee.ca]
Sent: Thu 3/1/2007 2:33 PM
To: Bricolage Users
Subject: how to file a feature request ticket?



Hi I just went to
>
>   http://bugs.bricolage.cc/

and am looking for a way to how  feature request ticket or
perhaps 
'add a request' in other parlance.

I only see a way to make a bug report, but no way to
indicate this is 
not a bug but a request. I've gone through the documentation
too.

thank you

Dawn

Ah thank you.

Dawn

On 1-Mar-07, at 11:34 AM, Beaudet, David P. wrote:

>
> I think that after you fill out the "bug
report", you'll be able to  
> categorize it as an enhancement request.
>
> ________________________________
>
> From: Dawn Buie [mailto:dawnthetyee.ca]
> Sent: Thu 3/1/2007 2:33 PM
> To: Bricolage Users
> Subject: how to file a feature request ticket?
>
>
>
> Hi I just went to
>>
>>   http://bugs.bricolage.cc/
>
> and am looking for a way to how  feature request ticket
or perhaps
> 'add a request' in other parlance.
>
> I only see a way to make a bug report, but no way to
indicate this is
> not a bug but a request. I've gone through the
documentation too.
>
> thank you
>
> Dawn
>
>

 
What's the best way to force a behind-the-scenes preview of
a story when changes to a story are saved?
 
The problem I'm experiencing is that even though my
templates are blazing the other dependent stories at
preview-time, if a user saves changes, but never previews a
story, the files on the preview server aren't updated and if
the user happens to navigate to those stories via another
path, the content is "stale"...
 
This isn't a problem with "publish" because users
must actively publish stories whereas previewing is optional
right?
 
If you think I'm worrying needlessly and that this is best
handled through user training, please let me know as well.
 
 
 
 

The same question has come up in our shop.  In our
situation, we are 
previewing on a separate server, and for our programmers
doing app 
development, making that preview is one extra step they wish
to avoid.

>
>What's the best way to force a behind-the-scenes preview
of a story 
>when changes to a story are saved?
>
>The problem I'm experiencing is that even though my
templates are 
>blazing the other dependent stories at preview-time, if
a user saves 
>changes, but never previews a story, the files on the
preview server 
>aren't updated and if the user happens to navigate to
those stories 
>via another path, the content is "stale"...
>
>This isn't a problem with "publish" because
users must actively 
>publish stories whereas previewing is optional right?
>
>If you think I'm worrying needlessly and that this is
best handled 
>through user training, please let me know as well.
>
>
>
>


-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537

You can use `bric_soap workflow --to-preview .... publish`
to do bulk previewing,
but there's no functionality in Bricolage that previews when
you save.
(Here at least, that would be hideously slow.)

On Mon, 5 Mar 2007, Matt Rolf wrote:
> The same question has come up in our shop.  In our
situation, we are 
> previewing on a separate server, and for our
programmers doing app 
> development, making that preview is one extra step they
wish to avoid.
>
>> 
>> What's the best way to force a behind-the-scenes
preview of a story when 
>> changes to a story are saved?
>> 
>> The problem I'm experiencing is that even though my
templates are blazing 
>> the other dependent stories at preview-time, if a
user saves changes, but 
>> never previews a story, the files on the preview
server aren't updated and 
>> if the user happens to navigate to those stories
via another path, the 
>> content is "stale"...
>> 
>> This isn't a problem with "publish"
because users must actively publish 
>> stories whereas previewing is optional right?
>> 
>> If you think I'm worrying needlessly and that this
is best handled through 
>> user training, please let me know as well.

>You can use `bric_soap workflow --to-preview ....
publish`
>to do bulk previewing,
>but there's no functionality in Bricolage that previews
when you save.
>(Here at least, that would be hideously slow.)

Any particular reason for that slowness?

-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537

On Mon, 5 Mar 2007, Matt Rolf wrote:
>> You can use `bric_soap workflow --to-preview ....
publish`
>> to do bulk previewing,
>> but there's no functionality in Bricolage that
previews when you save.
>> (Here at least, that would be hideously slow.)
>
> Any particular reason for that slowness?

Because the templates are run. 
(And remember that's for every output channel, and you're
going
to FTP the files over a network - every time someone
saves.)