Front Page Team Speak Overview.

[Tbar]

FireStorm,

Using FireFox.
Front page Team Speak Overview when clicked brings me to the central launch pages (log-in page). Yet if I open that link in a new tab, it works correctly.

I have screen shots if needed.

I'm wondering if that is some sort of "naming" problem where something I did prio too.. is causing that unwanted affect on the USAAC Site. No problem on the central launch site that window comes up correctly.

What can I do on my end to correct that.. or is it a website problem?

/tbar

[Firestorm]

Hi Tbar,

I am not getting that problem at all and cant replicate it. Not sure why it would be doing that as the link goes directly to the correct area.

http://www.airattack-central.com/teamspeak.php

Fire

[Tbar]

Yes, the link is correct. If I open that link in a new tab .. works just fine. I have not had this problem at all until the TS was changed for USAAC. Is there something on my browser involved or a naming convention for the module/pop up window?  I am miffed on this.

Here are the screen shots... maybe this might give a clue?


http://tbar.com/offsite/temp/usaac_fp_tso_0.jpg

It loads the clp.. lol, I can even log in :)


http://tbar.com/offsite/temp/usaac_fp_tso_1.jpg

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

 
Thanks
/tbar

[Firestorm]

Hi Tbar,

That is a weird one for sure. Haven't seen anything like that before and I don't know why it should happen so suddenly. I doubt the module has anything to do with it as its address is the central site and not ours.

When I hit that link I get the window opening up in another full tab rather than a small popup but I don't think that would cause the problem you have either.

You got me stumped on that one but I will try and find a solution to it.

FYI...I will be away as I need to have surgery this morning but should be back on deck in a couple of days. Nothing serious just a biopsy to find out if I have sarcoidosis.

Talk soon mate

Fire

[Tbar]

Fire,

Thanks for taking the time. Yes.. its a bugger alright and when we figure this out it will turn out to be a really simply thing.. lol. I hope its not a complicated fix. Yea.. I have no idea either. They key is it didn't start doing this until we changed Team Speak host, and I know the problem is NOT related to the host, but possibly some code change we made.

Good Luck with the hospital visit. Those visits scare me...

Ok.. open ticket that gets solved when it gets solved.

Thanks
Tbar