It depends on if you wanted to store the file contents in the database in an encoded format. I only mentioned this because before revision 1724 updates.php was trying to decode it when retrieving the file but FOGConfigurationPage.class.php never encoded it when it saved it.
As of revision 1726, the file is not encoded when its stored, but it is decoded when it’s retrieved, so it corrupts the file. Either FOGConfigurationPage.class.php lines 544 and 552 will need to encode the data before it’s stored, like:
[code]->set(‘file’,base64_encode(file_get_contents($_FILES[‘module’][‘tmp_name’][$index])));[/code]
or updates.php line 20 will need to have the decode statement removed from it:
[code]print $ClientUpdate->get(‘file’);[/code]
but only one of those options. Sorry for the confusion! 😞