Doc #76132 [Csd->Nab]: Documentation lacks a warning about file_put_contents()

Edit report at https://bugs.php.net/bug.php?id=76132&edit=1 ID: 76132 Updated by: requinix@php.net Reported by: briethings at gmail dot com Summary: Documentation lacks a warning about file_put_contents() -Status: Closed +Status: Not a bug Type: Documentation Problem -Package: Documentation problem +Package: Filesystem function related Operating System: any PHP Version: 5.6.34 Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2018-03-22 02:59:07] briethings at gmail dot com Sorry, you're totally right! However I had error_reporting set to E-ALL, but I fell into a stupid but interesting pitfall (so I'll report it to user-notes instead of bug!). Here it is: the $filename arg was coded as $path.$file, with say $path = 'path/to' and $file = 'file.txt'. You see that $path lacks its ending "/", so the resulting full path was 'path/tofile.txt': so file_put_contents() didn't fail but created the 'tofile.txt' in the *parent* directory of the one where I expected it, making me believe that nothing had happened! Again, sorry for the false alert, and thanks for your vigilance. ------------------------------------------------------------------------ [2018-03-22 01:58:25] requinix@php.net You sure? Because on Windows I see > Warning: file_put_contents(...): failed to open stream: No such file or directory Maybe you have warnings hidden? Check your display_errors, error_log, and error_reporting settings. ------------------------------------------------------------------------ [2018-03-22 00:11:43] briethings at gmail dot com Description: ------------ --- From manual page: http://www.php.net/function.file-put-contents --- Documentation doesn't mention that, if the directory specified in $filename doesn't exist, file_put_contents() *silently* fails, with not even a notice. This can lead to situations where it may take time before realizing there is a simple type error! So IMO, at least this should be mentioned, or a notice should be thrown. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=76132&edit=1