First, in my image, if you go to a page and then go to lunch, come
back and hour later and click a link you get dropped back to the
front page because your session has expired. But I thought Pier
used the URL to be able bookmark, surf the side via URL etc. In
fact, I thought it even worked this way before I put the security
Yes, it should work and remember the page even if the session expired.
Has this been fixed? It seems like if you click on a link that has
a URL, but an old session Pier could just make a new session and
apply that to the page the user is trying to go to. If the user is
not allowed to see that resource with the blank session then kick
them back to the front like now, but if the page is not restricted
they should see it.
This is a bug in Seaside. I fixed it, and the scenario you describe
works when you load the latest version:
Time: 30 January 2007, 11:23:44 pm
Second, is there any plan to expand on the RESTfulness of Pier? I
mean, I'm not a die-hard REST person or anything, but there are
times it would be nice to use URL's. I think the above suggested
handling would probably be enough.
Yep, that's a requirement. Thanks that you reported this, I probably
wouldn't have noticed it myself.
One thing that makes me want this is the difficulty of pointing to
another page in your Pier site from a custom component. I know you
have the #goto: message on anchor, but (1) I need it anywhere a URL
could be used, since I am using "html tag:" to do some tags not in
seaside (an HTML image map to be specific). And (2) the #goto:
message expects a structure that can be tough to get a hold of
sometimes. The easiest thing for me would be if I could simply
point my image map at the URL as a string, since that part is
public and I don't care if the user is logged in or not.
Glad that you ask. For the blog component I also felt the need to
have just the url and not only an anchor. I think I will need to add
that sooner or later. Shouldn't be too difficult though.
And lastly, I have had some users complain about the ugly URL's.
know you can say that they shouldn't look at the URL, etc. etc.,
but if we can make this better why not?
What I was thinking was, how hard would it be to change Pier so
that the URL part stays, but at least the session (and maybe the
command and view fields as well) could optionally be cookies. And
this could even be something configured in the /seaside/config/pier
Go to the Seaside configuration page and enable 'Use Session
Cookies'. This will put the session key into a cookie, if possible.
Thanks in advance. You may have ways to do all these things by
now, but I thought I would check.