Re: [PHP] Problem appending data in a file with fopen(ftp://...,a)

I got the same error message when i opened it with w... A append operation opens the file in r/w? I'm not sure... I though it needed a + : a+, w+... anyway, I think I'm gonna use a database (mysql) and it will be easy to to what I need but this problem is very strange. Thanks! Aha -- I

[PHP] Problem appending data in a file with fopen(ftp://...,a)

I am able to create the file when it is not already there but I got a file exists error when I try to fopen it in append mode the second time. I wrote this to store a log of the traffic on my site (userid in a cookie+timestamp) in a file. Don't know if i'm using the good technique but it's very

Re: [PHP] Problem appending data in a file with fopen(ftp://...,a)

On Sunday 28 October 2001 06:41 pm, you wrote: Is it possible to solve this problem or it's a feature in PHP? If I understand your problem, you are trying to open the same file twice. I'm not sure why you would want to do that, but assuming you have a good reason, you need to make sure you

Re: [PHP] Problem appending data in a file with fopen(ftp://...,a)

I only fopen my file once... My program checks if there is a specific session cookie. If not (it's a new user that browse the site) I set a cookie and try to store the unique ID of this user (other cookie) in a file with a timestamp to track which user came and when (+ nb of times...). That's

Re: [PHP] Problem appending data in a file with fopen(ftp://...,a)

On Mon, 29 Oct 2001 13:59, Dave Létourneau wrote: I only fopen my file once... My program checks if there is a specific session cookie. If not (it's a new user that browse the site) I set a cookie and try to store the unique ID of this user (other cookie) in a file with a timestamp to

Re: [PHP] Problem appending data in a file with fopen(ftp://...,a)

On Sunday 28 October 2001 07:29 pm, you wrote: I only fopen my file once... My program checks if there is a specific session cookie. If not (it's a new user that browse the site) I set a cookie and try to store the unique ID of this user (other cookie) in a file with a timestamp to track