|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

0rlin
|
Posted - 2010.03.17 23:36:00 -
[1]
I am having an issue running the cron, I am getting this error.
TS interface error: invalid serverID
Now everything is working but the cron
|

0rlin
|
Posted - 2010.03.18 13:35:00 -
[2]
the port is not the default, its changed. Is it hard coded in the cron or is it using the config?
|

0rlin
|
Posted - 2010.03.18 23:24:00 -
[3]
Edited by: 0rlin on 18/03/2010 23:27:09 Getting the same error |

0rlin
|
Posted - 2010.03.20 19:35:00 -
[4]
Well running this is returning to a blank page. Deleting all my registered accounts from the API table and removing them from the server group.
They should not be getting deleted and removed since they are getting setup with the same config.
|

0rlin
|
Posted - 2010.03.21 15:27:00 -
[5]
Edited by: 0rlin on 21/03/2010 15:29:27 Debug: UID = KEY WAS HERE
Debug: Information = UserID APIKEY CharacterID were all here.
Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 5: parser error : Start tag expected, '<' not found in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 33
Warning: simplexml_load_string() [function.simplexml-load-string]: in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 33
Warning: simplexml_load_string() [function.simplexml-load-string]: ^ in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 33
Notice: Trying to get property of non-object in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 34
Notice: Trying to get property of non-object in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 34
Notice: Trying to get property of non-object in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 35
Notice: Trying to get property of non-object in D:\vhosts\MYDOMAIN\subdomains\tsreg\httpdocs\cron.php on line 35
Checking: -
User not in alliance: - Alliance: - Corp: - uid: KEY - cid: 2
User removed from TeamSpeak access. New alliance is now: .
It is doing this for everyone registered. Now the verify worked to register. I also tested to make sure that it was not because tickers were changed once they were registered so thats not the problem.
|

0rlin
|
Posted - 2010.03.21 16:12:00 -
[6]
That code snip is not in my cron and I am running 1.3 I do beleave its the lates but I did just try to download from the link on the first post and it seems to be broken
|

0rlin
|
Posted - 2010.03.21 16:19:00 -
[7]
Edited by: 0rlin on 21/03/2010 16:21:49 I verified its constructing the $url correctly by adding the following if ($c->verbose == true) echo "<p>Debug: Information = ".$url."</p>";
Here is lines 28 - 35
$xml = simplexml_load_file($url); if (!empty($xml->error)) { if ($c->verbose == true) echo '<p>API Error: Cannot obtain information! Assuming user is OK.</p>'; } else { $xml = simplexml_load_string($xml); $corpid = (int) $xml->result->corporationID; $username = $xml->result->name;
|

0rlin
|
Posted - 2010.03.21 23:44:00 -
[8]
Thank you that seems to be working.
How hard would it be to have it look to see if you have Director Roles and add you to another group and then take it away if your no longer a director or you leave corp/alliance
|

0rlin
|
Posted - 2010.03.23 21:47:00 -
[9]
Need to not allow them to register multi times just because they change ts3 IDs
Perhaps look for the API info and do not continue if its already used.
|

0rlin
|
Posted - 2010.03.23 22:03:00 -
[10]
Notice: Trying to get property of non-object in D:\vhosts\mydomain\subdomains\tsreg\httpdocs\functions.php on line 175
Fatal error: Call to a member function attributes() on a non-object in D:\vhosts\mydomain\subdomains\tsreg\httpdocs\functions.php on line 175
The only thing different from him and many others is that he has an ' in his name.
|
|

0rlin
|
Posted - 2010.03.24 00:59:00 -
[11]
I started to debug it and stripslashes but then just turned of magic_quotes on the server. However i guess it would be better if I added it to the code.
|

0rlin
|
Posted - 2010.03.24 12:40:00 -
[12]
All it would need to do is look to see that the userID of the API info is already posted. At that point it could offer them to change there ts3 ID.
I had created a .NET app that controls all logins needed fro forums, ts2, ts3, openfire, mirc and more as needed. It would do all this from one ingame registration using the API info. The reason I point this out is that my method was different than yours. Where I would verify the API ingame and then create the accounts.
TS3 account was created by having them pasting there uniqueID into a field and submitting it. This allowed me flexibility to watch for people trying to register multiple ts3 uniqueIDs and if they did they would be stopped and prompted them to edit/change the uniqueID. This added security and allowed them to fix there account if they reinstalled without exporting there identity from ts3.
|

0rlin
|
Posted - 2010.03.25 12:26:00 -
[13]
Originally by: Agent Unknown
To be honest, I don't see the difference. If they have to give the userid and API again in order to register, then it's pointless to change the ID because of the way TS3 works (every ID is a new "user"). If anything, the script should return an error if the API is already being used to prevent abuse of stolen API information. This and a few other things are being worked on for the next version, but school has been murder the past couple weeks.
There's also a method of using the in-game browser to verify, but the fields used can be easily spoofed, so I can't rely on that for security.
If you just return an error if they are already registered then how do you recover when someone reinstalls there client and gets a new ts3 uniqueID? It makes no sense to me to allow them multi registered accounts. But at the same time you need to allow for them to recover from there uniqueID change. Yes you can spoof the url of the in-game browser however it makes no difference from what your doing now. If they have the API of someone and want to use it there is nothing stopping them ATM. However that will change. Because we will soon have a way of sending in-game mails from out of game. So an eve-mail confirmation could be sent or even a hash verifier..
|
|
|
|