error report

[GoogleCodeExporter]

Message: Cannot parse arena report!
Exception caused by Error: ARENA_GLADIATORS cannot be parsed.
No valid xPath found.
message: ARENA_GLADIATORS cannot be parsed.
No valid xPath found.
fileName: chrome://gft/content/gft-main.js
lineNumber: 348
stack: getNodeContent([object 
Object],2,false)@chrome://gft/content/gft-main.js:348
parseArenaReport()@chrome://gft/content/gft-main.js:405
pageload([object Event])@chrome://gft/content/gft-main.js:384
([object Event])@chrome://gft/content/gft-main.js:589
([object Event])@chrome://gft/content/gft-main.js:608

name: Error

Original issue reported on code.google.com by [email protected] on 4 Jul 2011 at 5:57

[GoogleCodeExporter]

Same problem here. It occurs after an arena fight, started with the button in 
the profile:

Bericht: Cannot parse arena report!
Exception caused by Error: ARENA_GLADIATORS cannot be parsed.
No valid xPath found.
message: ARENA_GLADIATORS cannot be parsed.
No valid xPath found.
fileName: chrome://gft/content/gft-main.js
lineNumber: 348
stack: getNodeContent([object 
Object],2,false)@chrome://gft/content/gft-main.js:348
parseArenaReport()@chrome://gft/content/gft-main.js:405
pageload([object Event])@chrome://gft/content/gft-main.js:384
([object Event])@chrome://gft/content/gft-main.js:589
([object Event])@chrome://gft/content/gft-main.js:608

name: Error

Original comment by [email protected] on 14 Jul 2011 at 8:23

[GoogleCodeExporter]

Issues must be caused by Gladiatus update. As add-on is no longer supported by 
developer, changes seem unlikely.

Original comment by [email protected] on 14 Jul 2011 at 12:07

[GoogleCodeExporter]

Bericht: Cannot parse circus turma report!
Exception caused by Error: CIRCUS_DEFENDER cannot be parsed.
No valid xPath found.
fileName: chrome://gft/content/gft-main.js
lineNumber: 348

Original comment by [email protected] on 16 Jul 2012 at 2:57

[GoogleCodeExporter]

me to.

Original comment by [email protected] on 5 Feb 2013 at 6:20