:
>Hi Ramy,
>
>I just checked-in a fix - could you please test, if it now works for
>you?
>
>Thanks
>Carsten
>
>>-Original Message-
>>From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
>>Sent: Wednesday, August 21, 2002 3:15 PM
>>To: [EMAIL
Hi Ramy,
I just checked-in a fix - could you please test, if it now works for
you?
Thanks
Carsten
> -Original Message-
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 3:15 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Portal questio
Ramy Mamdouh wrote:
>
> Hello Carsten,
>
> It seems I don't have any problems in my coplets.
> And to be sure, I just tried to remove the "raw" sub-protocol from the
> sample portal (Sunsoptdemo), and it didn't work as well, giving the same
> message ("The coplet is currently not available") in t
Hello Carsten,
It seems I don't have any problems in my coplets.
And to be sure, I just tried to remove the "raw" sub-protocol from the
sample portal (Sunsoptdemo), and it didn't work as well, giving the same
message ("The coplet is currently not available") in the coplets I
removed the "raw"
Ramy Mamdouh wrote:
>
> Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my
> coplets displayed.
> But when I changed to cocoon:/ without the raw, the portal displays the
> ("The content is not avilable now") message !
>
> Here's one of my coplets defintion.
>
>
>
Hi Carsten,
Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my
coplets displayed.
But when I changed to cocoon:/ without the raw, the portal displays the
("The content is not avilable now") message !
Here's one of my coplets defintion.
Ramy Mamdouh wrote:
>
> Thanks for replying, but handlesParameters just handles the parameters
> of the portal engine (like size, customize, etc).
True.
> And handlesParameters is true by default.
Yes.
>
> What I'm asking about is handling any other parameters passed with the
> main portal
Hi Matthew,
Thanks for replying, but handlesParameters just handles the parameters
of the portal engine (like size, customize, etc).
And handlesParameters is true by default.
What I'm asking about is handling any other parameters passed with the
main portal uri.
handlesParameters has no effect
Ramy,
the coplet needs to be configured to handle parameters. Check the
handlesParameters entry in the portal documentation. This is optional - so
you will need to turn it on using the portal tool or by editing the coplet
profile.
Matthew
--
Open Source Group Cocoon { Consulting, Trainin
Hi Paul,
well we wrote the portal components currently in Cocoon, so I guess I can
comment on them :-).
We originally (1 1/2 years ago) looked at JetSpeed (back then) but decided
we didn't want a solution that was an add-on to Cocoon. We wanted to
integrate a solution into Cocoon and do this wit
10 matches
Mail list logo
