permissions system is confusing

>> For example, it proves to be extremely easy to disable the ability to
>> logout.   How do I leave this ability for specific users and/or members of a
>> group.
>>
>> Also, at times, if I DO lose the ability to log out for a given user, I also
>> lose the ability to login, period.
> The login and logout actions are not affected by the permissions. It
> is very simple: if you are logged in you can only log out, if you are
> logged out you can only log in, period.
>
> Lukas
>
>

>> Also,  the login text in the footer is supposed to show the name that is
>> logged in, but  that disappears and all that hows is "user". E.G. one
>> instance shows  "Logged in as admin (change password?)" and the there shows
>> "Logged in as user (change password?)", even though I'm logged in as admin
>> in both instances of Pier.
> Not in my image.
>
>> One is running on the Pharo-Seaside 1-click image, which does show the user
>> name, while one is running on Squeak 4.1   with Seaside and Pier installed
>> using ConfigurationOfSeaside30, and it only shows "user".
> I am not sure if anybody is maintaining Pier on Squeak?
>

>>> One is running on the Pharo-Seaside 1-click image, which does show the
>>> user
>>> name, while one is running on Squeak 4.1   with Seaside and Pier
>>> installed
>>> using ConfigurationOfSeaside30, and it only shows "user".
>>
>> I am not sure if anybody is maintaining Pier on Squeak?
>
> The latest Seaside-Pharo 1-click application for the mac doesn't even
> include Pier, nor the  classes
> either.

>  On 9/26/10 2:06 AM, Lukas Renggli wrote:
>>> Yes, but the logout option disappears for a non-superuser.
>> Not in my image.
>
> happens in both the Squeak 4.1  and pharo Seaside 3.0 rc images, and
> in Seaside installed from a pristine Squeak 4.1 image using
> ConfigurationOfSeaside30.
>
>
>>> Also,  the login text in the footer is supposed to show the name
>>> that is
>>> logged in, but  that disappears and all that hows is "user". E.G. one
>>> instance shows  "Logged in as admin (change password?)" and the
>>> there shows
>>> "Logged in as user (change password?)", even though I'm logged in as
>>> admin
>>> in both instances of Pier.
>> Not in my image.
>>
>>> One is running on the Pharo-Seaside 1-click image, which does show
>>> the user
>>> name, while one is running on Squeak 4.1   with Seaside and Pier
>>> installed
>>> using ConfigurationOfSeaside30, and it only shows "user".
>> I am not sure if anybody is maintaining Pier on Squeak?
>>
>
> The latest Seaside-Pharo 1-click application for the mac doesn't even
> include Pier, nor the ConfigurationofSeaside, ConfigurationOfPier  
> classes either.
>
>
>>> Also, if I close the pier window from the browser when logout isn't
>>> showing
>>> and go back to the per entry point, I still can't login. I can clear
>>> the
>>> safari cache and/or quit safari numerous times, and I still can't
>>> log back
>>> in.
>> Again I cannot reproduce this on Pharo.
>>
>> Lukas
>>
> I'm going to have to install Pier on Seaside 3.0 final (Pharo) to test
> it. Will get back to you.
>

>> I'm going to have to install Pier on Seaside 3.0 final (Pharo) to test it.
>> Will get back to you.
>
> just installed pier2 via ConfigurationOfPier2  and
> ConfigurationOfPierAddOns2 on the latest version of Seaside 3.0 downloaded
> from seaside.st (Pharo version 1.1 latest update #11411)  and still get the
> same issue:   create a non-super-user, and the logout option goes away....
> permanently. Even if you quit and restart your browser and empty the cache,
> it still won't give the login option, so tweaking permissions for a
> non-superuser isn't an option.

>>> I'm going to have to install Pier on Seaside 3.0 final (Pharo) to test it.
>>> Will get back to you.
>> just installed pier2 via ConfigurationOfPier2  and
>> ConfigurationOfPierAddOns2 on the latest version of Seaside 3.0 downloaded
>> from seaside.st (Pharo version 1.1 latest update #11411)  and still get the
>> same issue:   create a non-super-user, and the logout option goes away....
>> permanently. Even if you quit and restart your browser and empty the cache,
>> it still won't give the login option, so tweaking permissions for a
>> non-superuser isn't an option.
> You need to clear the cookies to force a logout.
>
> As I said: "Indeed, but the result you describe is how it is configured by
> default: The owner and group of views and commands is 'admin', so you
> can only see those as 'admin'."
>