"Switch On" and "Switch Off" button is reversed
I can confirm this bug! It was introduced on
hfs24b6.exe (
hfs24b5.exe had this function working correctly). If you look carefully, the icon shows the correct function, meanwhile the text is wrong. I guess this happened to Rejetto when doing some automatic 'search and replace' on the source code, without looking if every replaced instance was the correct (it's something common, that it could happen to anyone).
could not reproduce the bug with Anonymous,
This is VERY weird! I'm pulling my hairs trying to reproduce the error, but now the bug is not coming back, neither using
{.!Anonymous.} or
{.!anonymous.}. There must be something with some specific configuration I had, but
now I can't reproduce this error anymore (is crazy!).
I've saved a screenshot yesterday (just in case), but anyway the bug
was not important, since it only was on the template (on client side), not on the HFS program (not on the server side, because the file gets renamed successfully anyway).
This was the error shown (see screenshot):
Error: {.break|result=bad session}
ok
But on the logs everything was normal:
19:42:22 127.0.0.1:2737 Requested GET /
19:42:25 127.0.0.1:2739 Requested GET /?mode=jquery
19:42:34 127.0.0.1:2740 anonymous renamed "/folder/SomeFile1.gif" to "SomeFile2.gif"
This error happened with some folder having the 'Hidden' flag, and the 'Upload' setting to 'Anyone'. Anyway, this error can't be reproduced anymore (but yesterday was solved only if
{.!anonymous.} in lower case was used).
But I've found another interesting things (two possible small bugs):
CASE 1) If you have an
empty 'hfs.ini', that file is IGNORED and the settings are saved directly on the registry (the file 'hfs.ini' is
deleted on exit, and the account 'can change password' is created normally).
Expected behavior: save all the settings on that empty 'hfs.ini'.
CASE 2) If you have a 'hfs.ini' file
with a minimal content (like a simple 'space' character, or containing a word like 'HFS' at start), the file is recognized and used to save the settings there (the registry is not used),
and if you already have a 'hfs.tpl' along with the 'hfs.exe' file, HFS is NOT creating the default account 'can change password' (if there is no 'hfs.tpl' file, the account 'can change password' is created normally.
Expected behavior: the account 'can change password' should be created and saved on the 'hfs.ini' file on this specific scenario (also the settings should be saved in a file, if an empty 'hfs.ini' file is found).
I hope this could be easily fixed...
Keep in touch if you need more details.
Cheers,
Leo.-