[MissKalunji]

Originally Posted by sv1cec

This issue has been beaten to death. There is a routine with the same name in inferno and in AWS. Rename one of the two to something else, and then fine every occurence of that name in the hack's files and change it to the new name.

Second, the cron job which is supposed to remove the warnings, as they mature, was not correct. It was using $vboptions instead of the new $vbulletin->options. I just uploaded a new file (kill_warns.php) which should work OK.

Folks, please understand that I no longer provide support for this hack, I've stated from the beginning of the 3.5 version, that I have lost interest in it, since the vB changes are too many and I do not plan to upgrade my board to vB 3.5, so I have no reason to work on this any more. However, I am doing all I can to solve the issues you bring up. This is not always possible, since I have no idea on how the new version of vB works or how the new version of AWS works (as far as the vB installation etc is concerned).



That should be in your postbit and postbit_legacy templates.

As for the other issue you have, these phrases are at the functions_warning.php file in the /includes directory.

well thank you