File name Bug

What special characters in particular are you seeing this error with? If you run FFMPEG from the command line, is FFMPEG able to read the file?

characters like &():!@#$% doesn’t work..
It also stopped in ssh…

root@sd-77321:~/bin# cd ~/bin && ./ffmpeg -i /var/www/vhosts/site.com/site.com/TEST&FILE.mp4 /var/www/vhosts/site.com/site.com/TEST-TEST/TEST&FILE.mp4
[2] 27430
[3] 27431
ffmpeg version 2.6.git Copyright (c) 2000-2015 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  libavutil      54. 26.101 / 54. 26.101
  libavcodec     56. 41.101 / 56. 41.101
  libavformat    56. 34.100 / 56. 34.100
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 16.101 /  5. 16.101
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  3.100 / 53.  3.100
FILE.mp4: command not found
FILE.mp4: command not found

[2]+  Stopped                 cd ~/bin && ./ffmpeg -i /var/www/vhosts/site.com/site.com/TEST
root@sd-77321:~/bin#

All of those characters are supposed to be filtered out of filenames and replaced with dashes when they’re added to the WordPress database. Allowing most of them, and the ampersand in particular, in strings that are executed on the server would be a security risk.

Did you add these to the database using the Add From Server plugin?

i see.. thanks for the info.
yes i used Add From Server plugin.
will “add_attachment” action do the trick? rename/filter new attachments.
there’s no documentation in WordPress though.
anyways ill just do more research about this..

I think by the time add_attachment is run, it’s too late because the file is already in place. Filtering add_attachment is just going to point the database to a file that doesn’t exist. When you use Add From Server are the files already in the WordPress uploads directory? Add From Server runs wp_unique_filename (which among other things calls sanitize_file_name) when copying files from other directories, but skips that step when the file is already in the uploads directory.