I can answer this from the point of view of the xml format and as a developer of Cradiator, which consumes the xml that CC.net outputs.
(You mentioned Cradiator but didn't say whether it was having issues or if it was displaying incorrectly).
I won't be able to solve anything to do with the CC.net web front-end, however.
Basically, the xml format changed between 1.4.3 and 1.5, so it's likely that some component of what you're using, hasn't been updated.
CC.net 1.4.3 was the first version to include breakers in the xml.
CC.net 1.5.x changed the xml format.
An example of the xml is below.
This example includes the old & new format for demo purposes.
Old - > the breakers were in the 'CurrentMessage' attribute - as a raw string, which had to be parsed)
CurrentMessage="Breakers: bsimpson, jsmith"
New -> the breakers were in a new xml element tree 'messages/message' where the attributes defined info about that particular message eg
<messages>
<message text="bobble, harry" kind="Breakers"/>
</messages>
Recent releases of Cradiator can read both these formats, so it should have no trouble.
If you can verify that your xml is the new format below (the xml is served at the url http://yourhost/ccnet/XmlStatusReport.aspx), then any issues may be old components (eg dlls?) not being able to read the new format.
The full example:
<Projects CCType="CCNet">
<Project name="Project 1" category=""
activity="Sleeping"
lastBuildStatus="Failure"
lastBuildLabel="1.4.1.3844"
lastBuildTime="2008-12-12T12:08:24.796875-06:00" nextBuildTime="2008-12-12T21:09:30.234375-06:00"
webUrl="http://ccnetlive.thoughtworks.com/ccnet/"
CurrentMessage="Breakers: bsimpson, jsmith"
BuildStage="">
<messages>
<message text="bobble, harry" kind="Breakers"/>
</messages>
</Project>
</Projects>