Ships & weapons used stats are wrong.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Problem already exists, on eve-kill

What is the expected output? What do you see instead?
I expect to see accurate stats on ships and weapons used by the
corporation, instead we get this:
http://gallente.eve-kill.net/?a=corp_detail&crp_id=11295&view=ships_weapons
Apparently we have used ships and weapons we cant use yet...

What version of the product are you using? On what operating system?
KB Source Version: 3.0.0
EVE Source Release: (Dominion)
EVSCO Revision: Dev 448

Please provide any additional information below.
I first noticed this after having upgraded our own Killboard to EDK 3.0.2
We got the same results as on eve-kill.
Funny thing is that the ships and weapons used stats are correct for
individual pilots.

Original issue reported on code.google.com by topalall...@acore.nl on 20 Apr 2010 at 10:05

[GoogleCodeExporter]

I'm fairly sure this describes your problem. If I've misinterpreted anything, 
please 
say so or I'll be fixing a different problem. :)

What steps will reproduce the problem?
1. Go to a corp detail page.
2. Click on the ships and weapons statistics.

What is the expected output? What do you see instead?
The ships and weapons shown should be those used by the corp and how many kills 
with 
each. Instead other ships are shown, which can even include ships not flown by 
the 
corp.

e.g. http://gallente.eve-kill.net/?a=corp_detail&crp_id=11295&view=ships_weapons

What version of the product are you using? On what operating system?
KB Source Version: 3.0.0
EVE Source Release: (Dominion)
EVSCO Revision: Dev 448

Please provide any additional information below.
I first noticed this after having upgraded our own Killboard to EDK 3.0.2
We got the same results as on eve-kill.
Funny thing is that the ships and weapons used stats are correct for
individual pilots.

Original comment by kovellia on 21 Apr 2010 at 11:37

• Changed state: Started
• Added labels: Milestone-Release3.1

[GoogleCodeExporter]

This issue was closed by revision r645.

Original comment by kovellia on 21 Apr 2010 at 11:39

• Changed state: Fixed