Sep 3rd, 2010, 8:53 AM
Hi Craven,
Hmm... historically, I've always found that if files aren't getting uploaded it's because of either of the following two causes:
1. the settings on the file field are two restrictive, e.g. they only permit file types of a certain format or size
2. the PHP config has been told to disregard files over a certain file size
You've probably checked into them, but if not I'd start there. If it's working sporadically, I doubt it's a problem with the FT upgrade or migration.... but still, doing a fresh install as a base test is never a bad idea.
Regarding the filename changes: yes, you're quite right about Form Tools occasionally renaming files. In the past, I received a number of bug reports in which files were uploaded with filenames that were valid on the system in which they were created, but not by the server that they get uploaded to. For example, if the file contained spaces, non-ascii or UTF-8 characters, it could cause any number of issues down the line. So to cover all scenarios, in 2.0.1 I added a new variable to library.php: $g_filename_char_whitelist
That specifies all the permissable characters in a filename, any other characters are stripped out. Feel free to override that setting, but don't override it there: just add that variable to your config.php so you can upgrade safely.
Hope you get to the bottom of this.
- Ben
Hmm... historically, I've always found that if files aren't getting uploaded it's because of either of the following two causes:
1. the settings on the file field are two restrictive, e.g. they only permit file types of a certain format or size
2. the PHP config has been told to disregard files over a certain file size
You've probably checked into them, but if not I'd start there. If it's working sporadically, I doubt it's a problem with the FT upgrade or migration.... but still, doing a fresh install as a base test is never a bad idea.
Regarding the filename changes: yes, you're quite right about Form Tools occasionally renaming files. In the past, I received a number of bug reports in which files were uploaded with filenames that were valid on the system in which they were created, but not by the server that they get uploaded to. For example, if the file contained spaces, non-ascii or UTF-8 characters, it could cause any number of issues down the line. So to cover all scenarios, in 2.0.1 I added a new variable to library.php: $g_filename_char_whitelist
That specifies all the permissable characters in a filename, any other characters are stripped out. Feel free to override that setting, but don't override it there: just add that variable to your config.php so you can upgrade safely.
Hope you get to the bottom of this.
- Ben