$files->tempDir() method

Return a new temporary directory/path ready to use for files

  • The temporary directory will be automatically removed at the end of the request.
  • Temporary directories are not http accessible.
  • If you call this with the same non-empty $name argument more than once in the same request, the same WireTempDir instance will be returned.

Example

$tempDir = $files->tempDir(); 
$path = $tempDir->get();
file_put_contents($path . 'some-file.txt', 'Hello world'); 

Usage

// basic usage
$wireTempDir = $files->tempDir();

// usage with all arguments
$wireTempDir = $files->tempDir($name = '', $options = []);

Arguments

NameType(s)Description
name (optional)Object, string

Any one of the following: (default='')

  • Omit this argument for auto-generated name, 3.0.178+
  • Name/word that you specify using fieldName format, i.e. [_a-zA-Z0-9].
  • Object instance that needs the temp dir.
options (optional)array, int

Deprecated argument. Call WireTempDir methods if you need more options.

Return value

WireTempDir

Returns a WireTempDir instance. If you typecast return value to a string, it is the temp dir path (with trailing slash).


$files methods and properties

API reference based on ProcessWire core version 3.0.236

Latest news

  • ProcessWire Weekly #554
    In the 554th issue of ProcessWire Weekly we'll check out the latest core updates, introduce a couple of new third party modules, and more. Read on!
    Weekly.pw / 21 December 2024
  • Custom Fields Module
    This week we look at a new ProFields module named Custom Fields. This module provides a way to rapidly build out ProcessWire fields that contain any number of subfields/properties within them.
    Blog / 30 August 2024
  • Subscribe to weekly ProcessWire news

“The end client and designer love the ease at which they can update the website. Training beyond how to log in wasn’t even necessary since ProcessWire’s default interface is straightforward.” —Jonathan Lahijani