Quote:
Originally Posted by Hawaiian-TV
I did it exactly as shown there (although the bottom two sections, for "Optional Input" and "Display Page"; there were no instructions for how to set these, maybe that's part of the problem?)
|
The defaults that are there are fine.
Quote:
Originally Posted by Hawaiian-TV
I keep getting the following message in the Manage Users page and at the bottom of the gTeamspeak main configuration page:
in a big black square that looks like a borderless console window.
|
You have enabled debug mode in advanced options. This is showing you the information that is happening when it is trying to connect to the teamspeak server to access live data via tcp.
Quote:
Originally Posted by Hawaiian-TV
This means I can't use any of the plugins and probably cannot auto-ban users from
the Teamspeak server when they are banned by usergroup. (?)
|
No, that is done by database access and if you can add members ok, they can be banned ok. The advanced options just allow you to do live things to the users like kick and message and obtain whois online information.
Quote:
Originally Posted by Hawaiian-TV
The other problem I'm having (probably related to the above one?) is that the Who's Online
part of the product isn't working for me. It's permanently stuck at "0 Active and 1 Inactive Users"
no matter how many people log in to both the site and the voice chat system or how long they stay
logged on. Everything else in both the TS server itself and the product seems to work perfectly so far though.
|
Yup, that is handled by the tcp connection for live data. You will have to enter a admin username and password to access tcp. The script is pretty smart, it can try and figure out the name and pass on its own and fill those values in automatically, and if it cant it will create a randomly named admin and pass for access. If you still cant access, it is probably due to something blocking the ports on the TeamSpeak server for tcp access. There are tools to determine the accessibility on the TeamSpeak forums.
The most important feature of the script, user access, will work just fine without tcp information. The tcp data is for fluff and fun, and unfortunately setting that up is something you will have to troubleshoot as there is no general fix all solution. There is a lot of information available on the TeamSpeak forums and I think Planet TeamSpeak has a port checking form on their site.
Good luck, thank you for the complements.