Probably worth pointing out that if you change the Public file system path to anything other than sites/default/files, it will not create the dataset file on the server. Not that I've been able to get to work, anyway.

Comments

bailey86’s picture

bailey86 commented

Hmmmm... - I thought that the code was supposed to pick up the current public files directory.

The directory is created with:

  // Create the default directory to hold the datasets.
  $dataset_directory_parent_directory = variable_get('file_public_path', conf_path() . '/files') . "/data_export_import";
  file_prepare_directory($dataset_directory_parent_directory, FILE_CREATE_DIRECTORY);

  $dataset_directory = variable_get('file_public_path', conf_path() . '/files') . "/data_export_import/nodes/";
  file_prepare_directory($dataset_directory, FILE_CREATE_DIRECTORY);

and later written to with:

    $file_name = format_date(REQUEST_TIME, 'custom', 'Ymd_His') . "_nodes_" . $content_type . ".dataset";
    $file_path_and_name = $dataset_directory . "/" . $file_name;

Could you possibly send through any further details?

One point to note - have you set that directory to be writable by the web server? Try

# chmod 777 /path/to/directory

and see if that resolves the issue.

bailey86’s picture

bailey86 commented

I'll test this on a dev server when I get chance.

bailey86’s picture

bailey86 commented

I'm busy as usual - would anyone be able to confirm whether or not the module works OK with a non-standard path for the files/ directory?

bailey86’s picture

bailey86 commented
Status: Active » Closed (works as designed)

I'm going to mark this as closed as I have had no feedback after my suggestion about permissions. Also, in the six months since release this issue has never been raised again.