Re: Concerning that big, big bug

Jagrata wrote:

> > All right, error still there.
> Is there a traceback? I presume the error is that
> no mail is sent when registering--Issue 01.
> Is that right?
> (need gforge...)

Attribute Error: setMemberProperties
that's all the traceback says. You can check it by trying to join.
The error does NOT come from mail issues, because I'm getting the same error
when I change the Plone settings to "no mail - choose your password".

> No you don't. If you need it in order to address the problem,
> then we have to give it to you and teach you how to work in
> the bash shell on Linux/FreeBSD. That is overhead I want to
> avoid. If it can't be avoided, then we stop, learn bash, and
> mark off dev areas on new staging server. Priydarshan would
> need to make this call.

Believe me, I do NOT want to have access to the filesystem.

> What methods on the filesystem raise errors?
> Can you supply a traceback?

see above.

> > I do not understand this problem as operating system related. Maybe I
just
> > don't understand what you guys are talking about, but my feeling is
> > definitely not that things go well on Windows and crash on Linux, if
that is
> > what you mean.
> You might be right. However, the eol problem we had recently
> was os related. The traceback showing "\r\n" in the python
> script revealed that.
>

Good point. Now what I'm doing at the moment is this: I create a totally new
installation of Plone on my machine, then I go through that Workflow-process
once again (I tell you , I'm really tired of this one ....) and then I'll
see at what point the error comes up - if it does.

I still feel somehow "responsible" for the error, because I was envolved
with membership issues, and it's a membership error that comes up. Really
bothers me...

Greetings
Dhyani


--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.