Re: fopen error [message #175233 is a reply to message #175230] |
Sun, 28 August 2011 16:07 |
eBob.com
Messages: 11 Registered: August 2011
Karma:
|
Junior Member |
|
|
Thanks A. I was able to find my dumb typo/logic error this morning. Thanks
for making me aware of the file_get_contents and file_put_contents
functions. I like to make my code as concise as possible.
Incidentally ... I am using single backslashes on the (Windows) command line
to specify file names and somehow that seems to be working fine. I'm using
PHP 5.3.
Thanks again,
Bob
"A" <a(at)a(dot)a> wrote in message news:j3dml8$3kh$1(at)gregory(dot)bnet(dot)hr...
>> $fpFileOut = fopen($fileout,"c");
>> if (!$fpFileOut) {echo "Error opening $fileout\n"; echo E-WARNING;
>> exit;}
>
> do an echo $fileout; before fopen to see what the folder/file is.
>
> remember the following:
>
> - in linux/unix the filenames are case sensitive and file system is a bit
> different than windows
> - when you define $fileout remember if you use backslashes you need to
> escape them so it is not
> $fileout = "c:\folder\file.txt";
> rather
> $fileout = "c:\\folder\\file.txt";
>
> in php you can use forward slashes instead which don't require escaping:
>
> $fileout = "c:/folder/file.txt";
>
> - you need to have write permissions (755, 666 etc.) if it is unix/linux
> system. many hosters set this for PHP but you haven't specified what kind
> of host you test this on.
>
> it is probably my lazyness, but unless you really need fopen you can get
> by just fine with much easier functions like readfile, file(),
> file_get_contents(), file_put_contents()... all work done in a single line
> rather than fopen, fread, fwrite, fclose.
>
|
|
|