Global fatal error.
 

Im trying to edit the usertool.php to enable some options but I dunno how to remove the global to enable it. If I dont edit it at all I get this:Fatal error: Call to undefined function: globalize() How do I get rid of global with the operation still working? Ive tried deleting the whole line with global but only to make the page show up but not function properly. I dont know what I should be doing in order to fix this so any help would be appreciated, thanks.

I think you need to be more specific about what you are doing - what does "remove the global to enable it" mean ? what "options" are you referring to ? - and what version of vb is this ?

Im using vbulletin 3.5.4 and when Im altering the usertools php. When I say remove the global, I meant the globalize part of the script say under search ip address. When I do this then I can access the page without the error stating itself BUT whenever I try to look up someones name or whatever, it doesnt follow through. I dont know what the undefined function is so that really confuses me on how to fix this. If im still being a little vague, tell me and Ill try to elaborate even more. Thanks.

globalize() doesn't exist in 3.5.x it's been replaced by the Vb_Input_CLeaner class

are used in 3.5.x instead of globalize()

So do I use that code to replace the globalize? Like wherever there is globalize, I use one of those? How do I know which one to use for where?

Is what you are trying to edit custom code? If so, post the segment here and we will help convert it for you to 3.5. If it's not custom code, then you can just upload the new file found in your 3.5.4 package. Globalize() is used in the 3.0.x series of vBulletin, so it shouldn't be in any of your files.

I think it stayed when it was upgraded from 3.0.6 to 3.5.4 Its the usertools located in the MODCp and when I tried giving some extra functions to the Mod CP I kept getting this error when I was testing it out. It is kinda odd that it would still be there after the upgrade though.

Reuploading the new 3.5.4 file should fix the solution, if you don't have any custom code in there that you need ported.