The last-utf-char-corruption still exists, but this cannot be seen on rejetto's computer.
Uploading a file with specified last utf8 char can reproduce the problem on most (other) computers.
eg. 哲学.ppt -> 哲�?ppt (note that dot disappeared too) Then "filename is forbidden".
yes, i tried this specific file name and it's working here.
What Windows version are you using?
I see in the screenshot that you are using a chinese translated HFS.
Can you try a clean one, without any customization, tpl, etc?
This seems can be fixed with the (almost) same way we used in alpha to the uploading function.
what are you talking about? i don't remember.
Maybe file names on windows are in ansi but not utf-8.
modern windows uses utf-16 internally, AFAIK.
it's me then converting it to utf-8 for some uses.
Another thing: Most of the templates of version 2.3 (including mine) seems cannot work correctly in 2.4, with bad file action functions. Should this solved by template makers or rejetto?
i expect 2.3 compatible templates to work, and I'll do my best.
Anyway, i tested takeback 0.13b, and it's using the experimental and undocumented _PASSWORD_MD5.
I don't think it's worth keeping it.
I thought you had it updated to the new method. Maybe I saw an old version? If yes, can you link me the new one?
Problems found in Takeback:
Uploads a blank file, no uploading results are shown (showing a filelist page while a POST request)
Renaming & moving do not work
Bad session when creating a folder
I just tried old 2.3 template, created a folder, uploaded a blank file (0 bytes), no problems found.
While testing takeback I saw a 'bad session'. Looked at the SID, and saw a '+' symbol, that was interpreted as a blank space by chrome while resending it.
I didn't dig it deeply, decided to just avoid it, and from next release the SID will have only alphanumerics.
But now I just cannot log in because of the problem i said above.