fwrite and fclose Error

Does it matter if the server is using LINUX or not? I noticed that they use LINUX and I've never done anything with LINUX, so I'm not sure if that could be the problem or not.

You need to chmod the folder with 0777 permission where you want to fwrite.

You need to chmod the folder with 0777 permission where you want to fwrite.

Thanks for the help. Okay, so how do I do it? This is what I tried. Is this right?

$file = "http://www.conway.cz/quizzes/XML/quiz001.xml";
chmod("http://www.conway.cz/quizzes/XML/$file", 0600);

I did that (and I tried 0777) and I got a new error:
Warning: chmod() [function.chmod]: stat failed for http://www.conway.cz/quizzes/ in /DISK3/WWW/conway.cz/www/quizzes/XML/XML_doc_processing.php on line 23

Thanks again, though, for the help. Am I doing it wrong?
P

You can do chmod using your FTP client. Right click on the folder/files that you need to set permissions.

Okay, I get it, so I set the permission. It was already set to 755, but I set it to 777 as per what you said and it still doesn't work. Maybe it's something in my code? It seems bizarre that it would work on my computer but not on their server. Any other ideas?

Okay, I figured out why it's not working. It's because of this function. This function is supposed to return the next file name. In the folder is a file called "quiz001.xml'. This function is supposed to return "quiz002.xml", but it's not working for some reason. It doesn't return anything.

function getNextFilename($dir, $prefix, $type) {
  // run some security checks on the arguments supplied
  if (!is_dir($dir)) return false;
  if (!preg_match('/^[-._a-z0-9]+$/i', $prefix)) return false;
  $permittedTypes = array('txt', 'doc', 'pdf', 'jpg', 'jpeg', 'gif', 'png', 'xml');
  if (!in_array(strtolower($type), $permittedTypes)) return false;
  
  // if the checks are OK, get an array of the directory contents
  $existing = scandir($dir);
  // create a search pattern for filenames that match the prefix and type
  $pattern = '/^'.$prefix.'(\d+)\.'.$type.'$/i';
  $nums = array();
  // loop through the directory
  // get the numbers from all files that match the pattern 
  foreach ($existing as $file) {
    if (preg_match($pattern, $file, $m)) {
	  $nums[] = intval($m[1]);
	  }
	}
  // find the highest number and increase it by 1
  // if no file yet created, assign it number 1
  $next = $nums ? max($nums)+1 : 1;
  // calculate how many zeros to prefix the number with
  if ($next < 10) {
    $zeros = '00';
	}
  elseif ($next < 100) {
    $zeros = '0';
	}
  else {
    $zeros = '' ;
	}
  // return the next filename in the series
  return "{$prefix}{$zeros}{$next}.{$type}";
  }

Yeah, it's this function because when I hardwire it with the next file name manually it works fine. It creates the file in the right place. So for some reason this function is returning nothing and I don't know why.

$dir = 'http://www.conway.cz/quizzes/XML';
$quiz_file = getNextFilename_file($dir, 'quiz', 'xml');

Your directory is: http://www.conway.cz/quizzes/XML

This is a URL, not a directory path.

PHP will create a HTTP socket to that URL (if allow_url_fopen is enabled in config).
What you want is for PHP to create a PHP socket to the file system. To do this either supply the absolute path, or relative path to that directory.

eg:

$dir = '/path/to/quizes/XML';

ie: scandir() the function used in getNextFilename() is a file system function, it cannot be used with a HTTP socket.

If you chmod() its is good practice to have the least permissions possible, but still allowing PHP to write to the file/directory. This can be achieved without giving the file a permission of 777, which means anyone on the server will be able to write to that directory (which is very insecure).

Here are some good resources on file permissions on Linux and Apache:
http://www.zzee.com/solutions/linux-permissions.shtml
http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch20_:_The_Apache_Web_Server

Thanks. Yeah, I was just going to write that I figured it out. That I was using the URL and not the path. Well, I didn't figure it out; the info guy at the server told me what was up. It was driving me crazy. And thanks a lot for the file permissions stuff. I was worried that I was opening myself up to a heap of trouble by using 777 for all of my folders and files. I got it working last night and I wrote my first file. Relief. Case solved. Thanks once more.