I forgot to mention, browsers cache the global.js file. Clear your cache and see if there's improvement.

Cleared the cache and still issues. I'm guessing the next step would be to re-upload the entire clientscript folder?

It can't do any harm. Again, I am operating mostly in the dark here. I am hoping someone with more knowledge sees this thread and chimes in.

How are you caching on the server?

There's a very small number of validation errors in your HTML. I always rule those out first when checking for problems like this.

I'm not even sure I fully understand what you are saying with the validation errors. I am no expert.

Check the article listed at the bottom of my profile about Validating vBulletin. You don't have that many, so it should be pretty easy to fix them and rule them out. Invalid HTML can randomly break JavaScript on a page.

Hi,

Am newbie here and run a forum called www.myfiatworld.com.
As of now I can see some Cold Z3ro and hackteach.org links at the bottom my forum transaction log/transaction stats area within admincp.It looks odd to me and hence a bit worried.

Hope some one will help me to get rid off this.

Thanks & Regards

Manoj

First you need to follow our advisory about deleting the install folder off your forums.

Then please read the following two blog posts:
http://www.vbulletin.com/forum/blogs...ve-been-hacked

http://www.vbulletin.com/forum/blogs...vbulletin-site

Also please see these recent security announcements:

vBulletin 4.1.x-4.2.x & All versions of vBulletin 5: http://www.vbulletin.com/forum/forum...-1-vbulletin-5
vBulletin 5.0.x patch released, for a different security issue: http://www.vbulletin.com/forum/forum...d-all-versions

Update: Back on topic.


Digital jedi, I tried the validation.. and I'm either failing completely at it or do not understand how it works.

It takes a bit of Googling sometimes. For the first error, I did cover that one in my article. No caps in most HTML code. That will probably fix THAT error. But like I mentioned in that article, you need to start with the top one and work your way down, as errors cascade. So fixing one can correct, or even reveal, others. Remember to check your code using Direct Input, as well, as the validator can't see the HTML generated to a logged in user.