Using Bricolage via External Dashboard

Hi everyone,

I'm working on developing a lightweight dashboard outside
bricolage,   
that gathers a list of stories via Soap request  
(Bric::Soap::Story::list_ids).   The goal here is to be able
to go  
directly to a story edit page within bricolage, from this  
dashboard.   I know of course, that linking to a URL that
would  
normally edit a page, the user gets kicked back to the
login, even if  
the user has already logged in.   Is there a way to directly
access  
such an edit story page by linking to it outside bricolage? 
Has this  
ever been done before?

I'd imagine it would have to do with manipulating the main
controller  
a bit.  Just wanted to get feedback from others who may have
done  
something like this before.

Thanks for your time

Paul

On Sep 13, 2006, at 10:22, Paul Kist wrote:

> I'm working on developing a lightweight dashboard
outside  
> bricolage,  that gathers a list of stories via Soap
request  
> (Bric::Soap::Story::list_ids).   The goal here is to be
able to go  
> directly to a story edit page within bricolage, from
this  
> dashboard.   I know of course, that linking to a URL
that would  
> normally edit a page, the user gets kicked back to the
login, even  
> if the user has already logged in.   Is there a way to
directly  
> access such an edit story page by linking to it outside
bricolage?   
> Has this ever been done before?

Be sure that the Window that opens the edit link URL in
Bricolage has  
the same name as the Bricolage Window. The window name is  
"Bricolage_SERVER_WINDOW_NAME", where
SERVER_WINDOW_NAME is the same  
as your VHOST_SERVER_NAME bricolage.conf directive with all
non- 
alphanumeric characters replaced with underscores (stupid
IE).

> I'd imagine it would have to do with manipulating the
main  
> controller a bit.  Just wanted to get feedback from
others who may  
> have done something like this before.

It hasn't been done that I know of, but I think that it's
just due to  
the window naming.

Best,

David

David,

Thanks, I'll give it a shot.

-Paul

On Sep 13, 2006, at 1:31 PM, David E. Wheeler wrote:

> On Sep 13, 2006, at 10:22, Paul Kist wrote:
>
>> I'm working on developing a lightweight dashboard
outside  
>> bricolage,  that gathers a list of stories via Soap
request  
>> (Bric::Soap::Story::list_ids).   The goal here is
to be able to go  
>> directly to a story edit page within bricolage,
from this  
>> dashboard.   I know of course, that linking to a
URL that would  
>> normally edit a page, the user gets kicked back to
the login, even  
>> if the user has already logged in.   Is there a way
to directly  
>> access such an edit story page by linking to it
outside  
>> bricolage?  Has this ever been done before?
>
> Be sure that the Window that opens the edit link URL in
Bricolage  
> has the same name as the Bricolage Window. The window
name is  
> "Bricolage_SERVER_WINDOW_NAME", where
SERVER_WINDOW_NAME is the  
> same as your VHOST_SERVER_NAME bricolage.conf directive
with all  
> non-alphanumeric characters replaced with underscores
(stupid IE).
>
>> I'd imagine it would have to do with manipulating
the main  
>> controller a bit.  Just wanted to get feedback from
others who may  
>> have done something like this before.
>
> It hasn't been done that I know of, but I think that
it's just due  
> to the window naming.
>
> Best,
>
> David
>

Paul Kist wrote:
> Hi everyone,
> 
> I'm working on developing a lightweight dashboard
outside bricolage, 
> that gathers a list of stories via Soap request
> (Bric::Soap::Story::list_ids).   The goal here is to be
able to go
> directly to a story edit page within bricolage, from
this dashboard.   I
> know of course, that linking to a URL that would
normally edit a page,
> the user gets kicked back to the login, even if the
user has already
> logged in.   Is there a way to directly access such an
edit story page
> by linking to it outside bricolage?  Has this ever been
done before?
> 
> I'd imagine it would have to do with manipulating the
main controller a
> bit.  Just wanted to get feedback from others who may
have done
> something like this before.
> 
> Thanks for your time
> 
> Paul
> 

You could try the approach we used for ASCA
http://freshmeat.
net/projects/asca/

Basically stuffing a user supplied username and password
into the web
service of your choice after authenticating from a source of
your choice.

I haven't tried this with Bricolage yet as we have no need
for all of
our users to login to it.  I haven't touched the code in a
couple of
years, so YMMV.

- cameron

On Wed, 13 Sep 2006, David E. Wheeler wrote:
> On Sep 13, 2006, at 10:22, Paul Kist wrote:
>> I'm working on developing a lightweight dashboard
outside bricolage,  that 
>> gathers a list of stories via Soap request
(Bric::Soap::Story::list_ids). 
>> The goal here is to be able to go directly to a
story edit page within 
>> bricolage, from this dashboard.   I know of course,
that linking to a URL 
>> that would normally edit a page, the user gets
kicked back to the login, 
>> even if the user has already logged in.   Is there
a way to directly access 
>> such an edit story page by linking to it outside
bricolage?  Has this ever 
>> been done before?
>
> Be sure that the Window that opens the edit link URL in
Bricolage has the 
> same name as the Bricolage Window. The window name is 
> "Bricolage_SERVER_WINDOW_NAME", where
SERVER_WINDOW_NAME is the same as your 
> VHOST_SERVER_NAME bricolage.conf directive with all
non-alphanumeric 
> characters replaced with underscores (stupid IE).

I think another problem is setting the authentication
cookie.
You can obtain a cookie by SOAP with for example

   bric_soap site --save-cookie-file cookie.txt list_ids

Inside the file cookie.txt, you'll find the cookies.
Not sure how best to set that in the browser.

On Sep 14, 2006, at 03:09, Scott Lanning wrote:

> I think another problem is setting the authentication
cookie.
> You can obtain a cookie by SOAP with for example
>
>   bric_soap site --save-cookie-file cookie.txt list_ids
>
> Inside the file cookie.txt, you'll find the cookies.
> Not sure how best to set that in the browser.

If they're already logged in, as Paul says, then they
should already  
have the cookie.

Best,

David

On Sep 14, 2006, at 03:09, Scott Lanning wrote:

> I think another problem is setting the authentication
cookie.
> You can obtain a cookie by SOAP with for example
>
>   bric_soap site --save-cookie-file cookie.txt list_ids
>
> Inside the file cookie.txt, you'll find the cookies.
> Not sure how best to set that in the browser.

If they're already logged in, as Paul says, then they
should already  
have the cookie.

Best,

David

That is a really good point, regarding the cookie.  If there
is a way  
to force login outside of Bric, that would actually
streamline the  
process even more.
I'll experiment with this and let you know how everything
turns out.

So far we're building this front-end component and it's
working out  
as planned.

I'll definitely keep you all posted.

Paul

On Sep 14, 2006, at 1:21 PM, David E. Wheeler wrote:

> On Sep 14, 2006, at 03:09, Scott Lanning wrote:
>
>> I think another problem is setting the
authentication cookie.
>> You can obtain a cookie by SOAP with for example
>>
>>   bric_soap site --save-cookie-file cookie.txt
list_ids
>>
>> Inside the file cookie.txt, you'll find the
cookies.
>> Not sure how best to set that in the browser.
>
> If they're already logged in, as Paul says, then they
should  
> already have the cookie.
>
> Best,
>
> David

On Sep 14, 2006, at 16:36, Paul Kist wrote:

> I'll definitely keep you all posted.

Yes, please do. It sounds interesting!

Best,

David

On Thu, 14 Sep 2006, David E. Wheeler wrote:
> On Sep 14, 2006, at 16:36, Paul Kist wrote:
>> I'll definitely keep you all posted.
>
> Yes, please do. It sounds interesting!

Yes, I'm also interested.