WAResponseGenerator>>expiredKey
by Nick Ager
Hi,
Selecting a different look using Pier's PRDesignChooserWidget causes
an WAUnregisteredHandlerError exception to be raised. This occurs on the
latest builds: http://hudson.lukas-renggli.ch/job/Pier%202/lastBuild/
The PRDesignChooserWidget registers 'pier' with the new structure in place
then sends an #expiredKey response as:
self requestContext responseGenerator
expiredKey;
respond
The problem appears to be in a change to WAResponseGenerator>>expiredKey,
which was introduced:
---
Name: Seaside-Core-YM.639
Author: YM
Time: 22 May 2010, 7:39:33 pm
UUID: e24bae83-3671-4679-ac8d-9f21154c304e
Ancestors: Seaside-Core-pmm.638
http://code.google.com/p/seaside/issues/detail?id=552
- Corrected WAResponseGenerator>>#expiredKey to always use the correct URL
- Implemented WAPathConsumer>>#upToEnd
----
The exception is thrown in the line:
url := self requestContext handler url.
#handler returns a WASession which I presume wasn't expected when the code
was written.
Changing the code to:
url := self requestContext request url
stops the exception from being thrown, but doesn't result in a URL free from
keys; not the desired effect. I found a handy Pier extension method
WAUrl>>purgeSeasideFields.The rewritten WAResponseGenerator>>expiredKey then
becomes:
expiredKey
"The session key has expired, redirect the request to the home directory
preserving the path as well as possible."
| url |
self request isXmlHttpRequest
ifTrue: [ ^ self forbidden ].
url := self requestContext request url.
url addAllToPath: self requestContext consumer upToEnd.
self request isGet ifTrue: [
url purgeSeasideFields].
self response redirectTo: url
With the requirement that the WAUrl>>purgeSeasideFields is moved from
Pier-Seaside-Mapping into Seaside-Core-HTTP.
Thoughts?
Nick
13 years, 3 months
changing a magritte description dynamically
by Nick Ager
Hi,
I have a form that's using generated via Magritte descriptions. I'd like to
be able to change the label on one of the fields dynamically. I thought I'd
found the solution by overriding #description on the instance-side and
editing the field's description as in:
description
| description pricePerUnitDescription |
self halt.
description := super description.
pricePerUnitDescription := description detect: [:each| each accessor
readSelector == #pricePerUnit].
self addCurrencyToDescriptionLabel: pricePerUnitDescription.
^ description
However it seems that the description is cached so this method is rarely
called.
Any thoughts on how to dynamically change the label in a magritte field
greatly received.
Thanks
Nick
13 years, 3 months
adding css id in magritte forms
by Sloan
Hello,
I'd like to add an id tag to a magritte generated form (like so <form
id="something" ...). Is there a chance to do this? I already know I can
assign a css id to a container around the form, but that's not what I want.
The seaside testing framework requires an id in the form.
Also, I am using the MACssRenderer in one of my models. However, if I subset
the descriptions to create a form magritte will use the table renderer
instead.
Regards
13 years, 3 months
Re: Pier site export - import
by dtrussardi＠tiscali.it
Thank,
from:
> http://www.lukas-renggli.ch/blog/export-import
>
i read:
Export the Site
Upgrade to the bleeding edge versions of Magritte and Pier. Also ensure that the package Pier-Squeak-Persistency is loaded and up-to-date.
Add the Import/Export component to one of your admin pages.
Read the instructions and click on Export to generate and download a complete snapshot of your site.
Now in gemstone i don't have load the Pier-Squeak-Persistency package.
And into http://seaside.gemstone.com/ss/pier i don't found any Pier-Squeak-Persistency entry.
I do test for Pier-Squeak-Persistency entry from http://source.lukas-renggli.ch/pier.
When i load Pier-Squeak-Persistency-kph.24 i found the error:
'This package depends on the following classes:
ImageSegment
You must resolve these dependencies before you will be able to load these definitions:
ImageSegment>>writeKernel:on:
'
Any idea ?
Thank,
Dario
13 years, 3 months
Re: smallwiki Digest, Vol 53, Issue 2
by Pablo Gancharov
> Message: 1
> Date: Tue, 1 Jun 2010 18:28:42 -0300
> From: Pablo Gancharov <pablogancharov(a)gmail.com>
> Subject: "Add a Note" addon to pier
> To: smallwiki(a)iam.unibe.ch
> Message-ID:
> <AANLkTinUnPhlr4ZWyD12E0xPO4z22jcQRprzdLQvJr7I(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello Lucas, The "User Contributed Notes" component that's shows on
> http://book.seaside.st/book/ it's a pier component?
> How can I add it to my pier site? Thanks.
>
13 years, 3 months
Pier site export - import
by dtrussardi＠tiscali.it
Hi,
i create a Pier site with the relative Gemstone implementation.
It's update to Pier 1.2.1.4 and work fine.
Now i'm interested to port it to a new Gemstone environment.
I can do save of the Pier 'structures' relative to my site ?
And after load it in a new environment ?
Any pointers would be greatly appreciated !
Thank,
Dario
13 years, 3 months
