| Bookmark this article at these sites |
|---|
|
)
And I must also give a pat on the back to the dev team. Not for fixing it, which should have happened in the first place so I see no reason to give credit there, but for going public and getting the word out so quickly about the issue.
The drama never stops somedays.
I for one appriciate any and all bug fixes. I even get a kick out of the drama queens that have less of a life than I do. Thanks, I needed a good ROFL moment. .
However, I confess I have to agree with Herve's comment. For the benefit of new users I don't understand why updated files cannot be added to the current stable download, or alternatively a new incremental version created. It must be simple to do compared to the hard work you've put into fixing the problem. Because there will be a 2.0.10 beta release soon, and because it is only 3 files.
Herko
I can only go by their reactions here
I uploaded again the file mimetypes.inc.php and uploader from the new upgrade the 2.9.0.10 and now it works I am ashamed! Thanks again for your attention.
![Open in new window](javascript:CaricaFoto("http://www.joker.si/mn3njalnik/style_emoticons/default/ranting.gif");)
$err .= '<br />'.implode('<br />', $uploader->getErrors(false));
$err = _FAILFETCHIMG;
@Mithrandir. Do you write Xoops core files and patches with a Unix text editor, a Mac or a PC?
Uploading a file in ASCII tells the FTP server to convert the line endings from the format the operating system on your computer uses to the format that the operating system on the server uses.
Window systems use a two character LF / CR (line feed + carriage return) line ending.
Mac systems use a one character CR line ending character.
Linux systems use a one character LF line ending character.
If you upload a text file from your Windows PC to a Linux server, all of the LF / CR character combinations in the Windows text file will be automatically converted to LF characters when the file is saved on the server, so the server will be able to read the lines in it correctly. (The reverse happens if you download a text file in ASCII mode from the Unix server to your Windows PC.)
This can be crucial for some types of text files, because if they have the wrong type of line ending, the server won't be able to read them properly. A multi-line script may be seen as one long line, because the server doesn't see proper line ending on each line.
Uploading a file in BINARY tells the FTP server NOT to convert any characters at all, to just store the file as it was uploaded. You want this for files such as .zip or .tar.gz compressed archives (altering bytes within them will corrupt them), and graphic file formats (altering bytes within them will change your image and possibly render it unviewable).
Since PHP files are generally text scripts, they should be uploaded and downloaded in ASCII mode so the line ending characters are converted to the correct format.