file_put_contents
this may be obvious, but it took me a while to figure out what I was doing wrong. So I wanted to share. I have a file on my "c:\" drive. How do I file() it?
Don't forget the backslash is special and you have to "escape" the backslash i.e. "\\":
<?php
$lines = file("C:\\Documents and Settings\\myfile.txt");
foreach($lines as $line)
{
echo($line);
}
?>
hope this helps...
file
(PHP 4, PHP 5)
file — Leest het volledige bestand in een array
Beschrijving
array file
( string $filename
[, int $use_include_path
[, resource $context
]] )
Hetzelfde als readfile(), behalve dat file() het bestand in een array terug geeft. Elk element van de array komt overeen met een regel uit het bestand, met het newline teken er nog aan. Als het faalt, geeft file() FALSE terug.
Je kan de optionele use_include_path parameter gebruiken door hem op "1" te zetten, als je ook in de include_path wil zoeken voor het bestand filename .
<?php
// Leest een bestand in een array. In dit voorbeeld gaan we via HTTP om
// de HTML code van een URL te krijgen.
$lines = file ('http://www.voorbeeld.com/');
// Loop door onze array, en laat de HTML code zien als HTML code; ook de regel nummers.
foreach ($lines as $line_num => $line) {
echo "Regel #<b>{$line_num}</b> : " . htmlspecialchars($line) . "<br>\n";
}
// Een ander voorbeeld, een webpagina laden in een string. Zie ook file_get_contents().
$html = implode ('', file ('http://www.voorbeeld.com/'));
?>
Tip
Je kunt een URL als bestandsnaam gebruiken met deze functie als de "fopen wrappers" aan staan. Zie fopen() voor meer informatie.
Note: Elke regel in de resulterende array bevat het newline teken, dus je moet nogsteeds trim() gebruiken als je dat niet wilt.
Note: If you are having problems with PHP not recognizing the line endings when reading files either on or created by a Macintosh computer, you might want to enable the auto_detect_line_endings run-time configuration option.
Note: Vanaf PHP 4.3.0 kan je file_get_contents() gebruiken om de inhoud van een bestand als een string te krijgen.
Vanaf PHP 4.3.0 is file() binair veilig.
Warning
Deze functie is (nog) niet binary safe!
Note: Context support was added with PHP 5.0.0
Zie ook readfile(), fopen(), fsockopen(), popen(), file_get_contents() en include().
add a note
User Contributed Notesfile
d basin
15-Oct-2009 12:47
15-Oct-2009 12:47
PenguinMan98 at usa dot net
22-Apr-2008 12:49
22-Apr-2008 12:49
on file() and flock()
My supervisor came up with a brilliant plan to workaround the inability of the file() to work on a flock()'ed file.
We created a dummy file called lockfile.txt. We would flock() lockfile.txt. Once we had a lock on it, we used file() on the file we wanted to read, then altered the file and called fclose on both files.
jon+spamcheck at phpsitesolutions dot com
16-Apr-2008 10:03
16-Apr-2008 10:03
A user suggested using rtrim always, due to the line ending conflict with files that have an EOL that differs from the server EOL.
Using rtrim with it's default character replacement is a bad solution though, as it removes all whitespace in addition to the '\r' and '\n' characters.
A good solution using rtrim follows:
<?php
$line = rtrim($line, "\r\n") . PHP_EOL;
?>
This removes only EOL characters, and replaces with the server's EOL character, thus making preg_* work fine when matching the EOL ($)
vbchris at gmail dot com
16-Feb-2008 10:15
16-Feb-2008 10:15
If you're getting "failed to open stream: Permission denied" when trying to use either file() or fopen() to access files on another server. Check your host doesn't have any firewall restrictions in-place which prevent outbound connections. This is the case with my host Aplus.net
Reversed: moc dot liamg at senroc dot werdna
12-Jul-2007 11:25
12-Jul-2007 11:25
This note applies to PHP 5.1.6 under Windows (although may apply to other versions).
It appears that the 'FILE_IGNORE_NEW_LINES' flag doesn't remove newlines properly when reading Windows-style text files, i.e. files whose lines end in '\r\n'.
Solution: Always use 'rtrim()' in preference to 'FILE_IGNORE_NEW_LINES'.
info at carstanje dot com
28-Nov-2006 09:33
28-Nov-2006 09:33
Using file() for reading large text files > 10 Mb gives problems, therefore you should use this instead. It is much slower but it works fine. $lines will return an array with all the lines.
<?php
$handle = @fopen('yourfile...', "r");
if ($handle) {
while (!feof($handle)) {
$lines[] = fgets($handle, 4096);
}
fclose($handle);
}
?>
richardtcunningham at gmail dot com
11-Jul-2006 11:19
11-Jul-2006 11:19
justin at visunet dot ie's note of 20-Mar-2003 states
"Note: Now that file() is binary safe it is 'much' slower than it used to be. If you are planning to read large files it may be worth your while using fgets() instead of file()."
I tested fgets(), file_get_contents(), and file() on PHP 4.3.2 and PHP 5 and timed each to be under a second with over 200,000 lines. I do not know if he was testing extremely long lines or what, but I could not duplicate the difference that he mentioned.
jonathan dot gotti at free dot fr
01-Feb-2006 11:52
01-Feb-2006 11:52
you can use
$file = array_map('rtrim',file('myfile.txt'));
to remove annoying ending lines of the resulting array.
Nuts
19-Jan-2006 12:16
19-Jan-2006 12:16
WARNING ON WINDOWS:
file() function will add "\r\n" in to the end of the row, even if you use only "\n" char to make rows in the file!
On UNIX systems there is no such problem.
dir @ badblue com
12-Sep-2003 11:48
12-Sep-2003 11:48
Jeff's array2file function is a good start; here are a couple of improvements (no possibility of handle leak when fwrite fails, additional capability of both string2file and array2file; presumably faster performance through use of implode).
<?php
function String2File($sIn, $sFileOut) {
$rc = false;
do {
if (!($f = fopen($sFileOut, "wa+"))) {
$rc = 1; break;
}
if (!fwrite($f, $sIn)) {
$rc = 2; break;
}
$rc = true;
} while (0);
if ($f) {
fclose($f);
}
return ($rc);
}
function Array2File($aIn, $sFileOut) {
return (String2File(implode("\n", $aIn), $sFileOut));
}
?>
If you're generating your string text using a GET or POST from a TEXTAREA (e.g., a mini-web-text-editor), remember that strip_slashes and str_replace of "/r/n" to "/n" may be necessary as well using these functions.
HTH --dir @ badblue com
John
21-Jul-2003 01:32
21-Jul-2003 01:32
after many months of confusion and frustration, i have finally figured out something that i should have noticed the first time around.
you can't file("test.txt") when that same file has been flocked. i guess i didn't have a full understanding of what i was doing when i used flock(). all i had to do was move the flock() around, and all was well.
justin at visunet dot ie
20-Mar-2003 06:36
20-Mar-2003 06:36
Note: Now that file() is binary safe it is 'much' slower than it used to be. If you are planning to read large files it may be worth your while using fgets() instead of file() For example:
<?php
$fd = fopen ("log_file.txt", "r");
while (!feof ($fd))
{
$buffer = fgets($fd, 4096);
$lines[] = $buffer;
}
fclose ($fd);
?>
The resulting array is $lines.
I did a test on a 200,000 line file. It took seconds with fgets() compared to minutes with file().
andrea at brancatelli dot it
16-Mar-2002 08:16
16-Mar-2002 08:16
file() has a strange behaviour when reading file with both \n and \r as line delimitator (DOS files), since it will return an array with every single line but with just a \n in the end. It seems like \r just disappears.
This is happening with PHP 4.0.4 for OS/2. Don't know about the Windows version.
php@don't_spam_me
09-Feb-2002 09:56
09-Feb-2002 09:56
It appears that the file() function causes file access problems for perl cgi scripts accessing the same files. I am using Perl v5.6.0 in linux with PHP/4.0.4pl1. After running a php app using the file() function, any perl cgi trying to access the same file randomly dies returning an internal server error: premature end of script headers.
The simple fix is to use fopen(), fgets() and fclose() instead of file().