Logician
Mon 2nd Sep '02, 12:02pm
I catched a bug related to Admin CP/Setting section.
In Admin CP/ Settings, if you enter a value to an input or text field in this context:
$a['a']
it causes an T_STRING' or `T_VARIABLE' or `T_NUM_STRING' error in global.php while getting forum options from the Template table, thus effecting all forum pages.
Same error happens if " is used instead of ' but error doesnt occur if ", ' or $ sign is removed. So these entries do not give any errors:
$a[a]
a['a']
$ a['a']
In other words there is no check for text/input field entries in Admin CP settings and any data in PHP associative array format entered causes errors.
It's no surprise no one run into it before and it's gone unnoticed for a long time since it happens only you enter an associate array format text in settings. I catched it when working on a new hack and noticed that it exists in all vb versions I tested. I checked from v.2.2.2 to 2.2.7 and bug is there in all versions in between..
It's a small bug but I believe you would like to know, so I'm informing you anyway.
If you are too busy with v.3, holler and I'll work on it a little more and release the fix as well..
Regards,
Logician
In Admin CP/ Settings, if you enter a value to an input or text field in this context:
$a['a']
it causes an T_STRING' or `T_VARIABLE' or `T_NUM_STRING' error in global.php while getting forum options from the Template table, thus effecting all forum pages.
Same error happens if " is used instead of ' but error doesnt occur if ", ' or $ sign is removed. So these entries do not give any errors:
$a[a]
a['a']
$ a['a']
In other words there is no check for text/input field entries in Admin CP settings and any data in PHP associative array format entered causes errors.
It's no surprise no one run into it before and it's gone unnoticed for a long time since it happens only you enter an associate array format text in settings. I catched it when working on a new hack and noticed that it exists in all vb versions I tested. I checked from v.2.2.2 to 2.2.7 and bug is there in all versions in between..
It's a small bug but I believe you would like to know, so I'm informing you anyway.
If you are too busy with v.3, holler and I'll work on it a little more and release the fix as well..
Regards,
Logician