sys_get_temp_dir() not writeable on some shared hosts

[iflow]

On some shared hosts / webspaces the sys_get_temp_dir() is not accessable / writeable.
Therefore a new Template can not be generated. The following Exception is thrown:
"'Could not create temporary file with unique name in the default temporary directory.'"

$this->tempFileName = tempnam(sys_get_temp_dir(), '');

I think the path, where the temporary files are stored should be configurable. So you can easily create a temp folder on your webspace and let PHPWord store the temp files there.

Ugh. Thanks for the report, @iflow. Good point. I will implement some alternative.

@iflow, do you mean that sys_get_temp_dir() returns an absolutely valid path, yet tempnam() can't access it and returns false?

[iflow]

@RomanSyroeshko Yes that's what exactly happening

@iflow, could you please test the implementation?

Use Settings::setTempDir() or the ini-file setting to set user defined temporary directory.

[iflow]

Sry for the late response: I'm not sure how to use the new function.

\PhpOffice\PhpWord\Settings::setTempDir($tmpdir);

And I'm not sure if it would work, because Template::__construct has not changed. There is still the line with tempnam, which does not use the user defined temporary directory.

 $this->tempFileName = tempnam(sys_get_temp_dir(), '');

[andrew-kzoo]

I saw this issue and thought maybe the PclZip component needs to be configured to use this new Settings:setTempDir() temporary directory setting, too. See #265 for a bit more information.

I can't look into this presently. I wanted to put a note out there for others who have need for, experience with, or been troubled by pesky errors reading and writing files in the system temporary directory.

[iflow]

Hi, thanks @andrew-kzoo
I solved the issue with modifying the __construct of Template.php:

$this->tempFileName = tempnam(getcwd() . '/mytemp', 'phpWord'); // Custom fix

You see, I through my own temporary directory to the tempnam function to fix the issue. It's not a nice solution, because it does influence future PhpWord updates. However this workaround works and so far I'm happy with it.