Search found 4 matches

Go to advanced search

by iLOtUTa
Sat Mar 21, 2009 1:35 pm
Forum: UTStatsDB
Topic: Bad parse in database??
Replies: 10
Views: 7250

Re: Bad parse in database??

if OLstats is not the cause, maybe it's UTComp. But i can't fix them.So I'm going to use the fix via PHP :oops:
by iLOtUTa
Sat Mar 21, 2009 6:01 am
Forum: UTStatsDB
Topic: Bad parse in database??
Replies: 10
Views: 7250

Re: Bad parse in database??

Sorry if i'm annoying. I solved temporally using this code:

file: 'includes/loggameevents.php' - line: 274 after '$vehicle = substr($data[4], 0, 60);'
ADDED:

if (preg_match("/\d+$/",trim($vehicle),$arr) != false) $vehicle = substr($vehicle,0,strlen($vehicle)-strlen($arr[0]));


file: 'includes ...
by iLOtUTa
Sat Mar 21, 2009 2:31 am
Forum: UTStatsDB
Topic: Bad parse in database??
Replies: 10
Views: 7250

Re: Bad parse in database??

Do you think it's normal there are 5000+ rows in my "_weapons" table?! :oops:
That should be the problem :oops:

EDIT1:
If I'm not wrong, i think the problem are in the logs(by olstats). Example:

651.00 PA 17 NewNet_ShockRifle10 4 0 0
651.00 PA 17 NewNet_ClassicSniperRifle15 1 0 0
651.00 PA 17 ...
by iLOtUTa
Fri Mar 20, 2009 2:24 pm
Forum: UTStatsDB
Topic: Bad parse in database??
Replies: 10
Views: 7250

Re: Bad parse in database??

Hello, i have same problem and i'm still looking for the solution.
Atm i found the loop without an end that causes this problem.
The file is "includes/logsave.php", this the loop:

while($row = sql_fetch_assoc($result)) {
$num = $row["wp_num"];
if ($num > $maxweapon)
$maxweapon = $num;
$weapsg ...

Go to advanced search