[Gjallar] user creation from root login

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Gjallar] user creation from root login

florent trolat
On Gjallar :

I try to do

self newUser: 'toto'.

with an admin consol and I obtain

MessageNotUnderstood: ByteString>>canRead:'

I've tried to debug it but I have to understand your event mechanism and
  its seems to be hard for me at the moment...

I want to add a simple user to my gjallar application....

May be I've not understand something?

thanks for your help!

Reply | Threaded
Open this post in threaded view
|

Re: [Gjallar] user creation from root login

Göran Krampe
Hi!

(moving this to setools list, remove squeak-dev in any responses - the
Gjallar discussion is better held in setools.)

florent trolat <[hidden email]> wrote:
> On Gjallar :
>
> I try to do
>
> self newUser: 'toto'.
>
> with an admin consol and I obtain
>
> MessageNotUnderstood: ByteString>>canRead:'

Mmmm, obviously a String receives #canRead: instead of a Q2User.

> I've tried to debug it but I have to understand your event mechanism and
>   its seems to be hard for me at the moment...
>
> I want to add a simple user to my gjallar application....
>
> May be I've not understand something?

No, the above is correct.

> thanks for your help!

First of all - we should add an option to "debug" console errors on the
Squeak side instead of just returning the error as a String.

Evidently this is permission related and I think it is triggered by
someone having a Subscription on the "User added" event and somewhere
down there something goes awry. The Subscription code is being hacked on
by us right now -  a range of issues.

I will see if I can track it down. It would be great if you could supply
more info - like where it is being called. You can put a "self halt"
into the #newUser: method and then step through it on the server side.

regards, Göran

PS. We are doing a testdeployment this week. At the end of the week we
could gather all fixes together and push out a new release. But this
will mainly be a bug fix release.