8 Apr
2010
8 Apr
'10
12:28 p.m.
It seems the setting in the application "Use Session Cookie" is useless in
pier.
PRRestfulSession>>returnResponse: aResponse
self hasSessionCookie
ifFalse: [ aResponse addCookie: self sessionCookie ].
^ super returnResponse: aResponse
If I force the hasSessionCookie to return false than the behaviour I expect happens. Now
I'm asking myself is this something that is wrong in my installation? This things are
so severe that they must have been recognized if it is an error in pier.
Norbert
On 08.04.2010, at 10:12, Norbert Hartl wrote:
In
PRContext>>urlOn
there is
(self command isRestful and: [ html context session hasSessionCookie ])
ifTrue: [ url purgeSeasideFields ]
ifFalse: [
url
addParameter: '_n';
addParameter: (html callbacks
registerActionCallback: [ PRCurrentContext value: self.]) ].
At a first glance it looks like the new context is only set in the ifFalse: block. In my
installation hasSessionCookie is true even if I switch off session cookie in the app
configuration.
I loaded per with ConfigurationOfSeaside and version string '1.2.1.3'
Norbert
On 08.04.2010, at 09:10, Lukas Renggli wrote:
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
The other
component is simply:
renderContentOn: html
html text: (self context propertyAt: #forwardText ifAbsent: ['kein Text
vorhanden'])
Yeah, but maybe #context uses an old cached context? Can you check
which is returned from that method, "self context" or "ctx"? To me
it
looks like "self context" is returned, because there are several tests
that set properties and copy contexts, and they pass.
Lukas
Norbert
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki On 8 April 2010 08:21, Norbert Hartl
<norbert(a)hartl.name> wrote:
> I tried to do some tests about transferring data via context from one page to another
in pier. I did
>
> renderContentOn: html
> | ctx |
> self context propertyAt: #forwardText put: 'set on old context'.
> ctx := self context structure: (PRPathLookup start: self context structure
path: '/targetpage').
> ctx propertyAt: #forwardText put: 'set on new context'.
> html anchor
> goto: ctx;
> with: 'go'
>
> On the targetpage there is a component that reads the property from the context and
displays it. What makes me wonder is that under any circumstances the text being display
is "set on old context". Even if I press the link "go". Why is that
so?
>
> Norbert
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki