FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

VS2005 Add-In / API v1 Error

Unlike some others, I've installed the API and the Add-In, and both are working... sort of.

I can see my list of shared and personal filters. Our company currently has 14 shared filters. Precisely 5 of those filters work in the Add-In.

The other 9 do not, work. Instead of saying "All X cases in P with status of S that must be fixed for R", it says, in red:

API returned invalid <case>

Again, I've no idea why some of the filters are working and others are not. Any insights?
PWills Send private email
Tuesday, December 19, 2006
 
 
I've passed your post along to the developers, who will be taking a look.
Eric Nehrlich Send private email
Tuesday, December 19, 2006
 
 
A new version of the API is out on

http://www.fogcreek.com/FogBugz/KB/setup/InstallFogBugzAPI.html

which should fix your problem.
Joel Spolsky Send private email
Tuesday, December 19, 2006
 
 
I tried the updated API and I am still having two major problems.

More than one space in a row in the case title introduces a &nbsp; in the XML document which causes it to fail parsing. This causes the error in the VS plugin "API returned invalid <case>" when I select a filter that has cases with this problem. If you edit the case title and remove double spaces this goes away.

The second problem is that characters like the ampersand in a 'Project' or 'Area' cause the document to fail to parse because the contents of the <description> not are not escaped with the UnicodeClean function.

I sent emails with screenshots of these problems into customer support. I'm posting this here to explain why you may still get the "API returned invalid <case>" even after updating the API as suggested.
Justin Foster Send private email
Tuesday, December 19, 2006
 
 
I'm having the same issues, though I haven't identified what characters are throwing the XML off, but for the characters to not be escaped makes it currently unusable. Any quick fixes planned, or something to do ourselves to fix this?
Matt Hawley Send private email
Wednesday, December 20, 2006
 
 
Yep, that's another bug. We just fixed it and released a new version of the API.

Thanks for all the help! Sorry for the trouble!
Joel Spolsky Send private email
Wednesday, December 20, 2006
 
 
Are the first three versions of the API all V1.0?

Hmm...
Will Dean
Wednesday, December 20, 2006
 
 
Everything is working well now with the latest API. Both issues I mentioned have been patched.

Thanks for the update.
Justin Foster Send private email
Wednesday, December 20, 2006
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.