----- Original Message -----
From: "Emiliano" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 29, 2000 10:47 PM
Subject: Re: [midgard] blobs + mgd_auth_midgard
> On Mon, 29 May 2000, [ IGP Internet ] wrote:
>
> > but it's a neverending story, isn't it...
> > midgard complaints that $object->deleteattachment(string name) and
> > $object->delete_attachment(string name) are unimplemented or undefined.
> > mgd_delete_attachment(int id) works fine with me though...
>
> Just tried this and I see no problem. Where does the complaint turn up? In
> the browser, in the logs?
Really, it works as advertised now. Khm, but I'm sure it complained before.
I just hate things happening without a pattern
> > And another strange thing I don't understand, really. Uploading files.
> > Copied David's code 'as is', and it worked fine. Then it stopped
working.
> > Basta. Now, whenever I try to upload something, it bangs a warning:
> > 'Warning: Only 8192 bytes were written, expected to write <here goes the
> > real file size> in /etc/httpd/conf/midgard-root.php3 on line 18
(sometimes
> > it's line 0)'
> > Could it be it's a browser's bug (IE5) or what? I'm using a little
> > redirection on site, but that's way before file upload, and it was there
> > before, while upload worked. Confusion is nice word for this :)
>
> Is there enough space in the temporary upload directory? If it wasn't
> specified in php3.ini, man tempnam will tell you where.
temp dir is /tmp, and $userfile var of the uploaded file says temp location
of the file is /tmp/phpsomething, $userfile_name, size and mime type are
reported correctly too.
that would be ok, but nothing is actually written to /tmp, 30megs df
who could be responsible for such a behaviour?
and to make it worse, file upload is started to work ok, this minute. still
nothing in /tmp, but blobdir is filled ok , just don't know how long will it
last...and what caused the change...
btw nobody.nobody is allowed r&w in /tmp...
> > Could you explain mgd_auth_midgard() again? Emiliano said in one of his
msgs
> > that mgd_auth_midgard($usrname,$passwd,0) authorizes user w/o sending
the
> > cookie. What's the difference between 1 and 0 as last parameter, both of
> > them send me the cookie.
>
> That shouldn't happen. Does it make any difference if you use FALSE
> instead of 0?
It tries to send the cookie anyway, I even tried offering chocolate pudding
with cherry on top...
Name: MidgardLogin
Domain: kamiks-eko.igp
Path: /
Expires: pet, sij 01 2010 12:00:00 (that is Fri, Jan :)
Secure: No
Data: bWxhZGVuK2thbWlrczptbGFkZW4=
>
> > I tried authorizing with
> > mgd_auth_midgard($username,$password,0); and $midgar->user was 0. Then I
> > used header("Location: $midgard->uri"); and $midgard->user became
expected
> > user id. Same thing when logging user out.
>
> This I don't quite follow.
I'll try to explain...
before calling mgd_auth_midgard($u,$p,0), value of $midgard->user is 0,
which is correct, since no auth is required by default.
after calling mgd_auth_midgard($u,$p,0), value of $midgard->user is still 0,
which isn't what we'd expect ($u and $p are ok)
then i tried sending location header, same location, hoping that would
reload the page
after that, $midgard->user gets correct value. think of it now, that might
be connected to mgd_auth sending cookie, since cookie values are not seen
until next visit to the page, what do you think?
Vanja
> Emile
>
>
> --
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
