I don’t know whether I have a misunderstanding of the Unfuddle API or whether there is a bug somewhere. When I post curl with:

api/v1/projects/9404/activity.xml?limit=1
I receive an events array with two “audit-trail” elements.

api/v1/projects/9404/activity.xml?limit=2
gives an identical result.

The results are all the same through limit=5, then at limit=6, there are still 2 audit-trail items, but the second entry is different than in the limit=5 case.

When I go up to limit=20, I get 6 audit-trail entries.

Also, the docs indicate that the components of “events” will be of type “event” but I receive “audit-trail” components.

Thanks for your help,
Sam Reid

Sam,

Thanks for your report on this issue.

There was indeed a problem with the account and project activity XML feeds in the Unfuddle API. The problem has now been remedied.

You should find that the number of items now correctly corresponds with the specified limit. Additionally, all child nodes of the ‘events’ now have ‘event’ tags instead of the previously misnamed ‘audit-trail’ tags (as is specified in the Unfuddle API documentation).

If you have any other problems, please do not hesitate to let us know.

Thanks!

Joshua,

Thanks for your prompt attention to this issue. I have verified that the components are now correctly returning type “event” instead of “audit-trail”. However, I am still receiving a different number of entries than specified in the limit arg. Here is a table showing the requested limit, and the number of received entry components. The command I’m running is:

curl_717_1_ssl/curl.exe -k -i -u [username:password] -X GET -H “Accept: application/xml” https://phet.unfuddle.com/api/v1/projects/9404/activity.xml?limit=[limit]

limit events
1 1
2 1
3 1
4 1
5 1
6 1
7 1
8 1
9 1
10 1
11 1
12 1
13 1
14 1
15 1
16 2
17 2
18 3
19 4
20 5
21 6
22 6
23 7
24 8
25 8
26 8
27 8
28 8
29 8
30 9
31 10
32 11
33 12
34 13
35 14
36 15
37 16
38 17
39 18
40 19
41 20
42 21
43 22
44 23
45 24
46 25
47 26
48 27
49 28

Best Regards,
Sam Reid

Sam,

I see now what you were describing. I could not duplicate this problem yesterday. However, I have since discovered that the “limit” was occurring prematurely in the project activity feed (essentially truncating more than was necessary).

I have just deployed a fix for this. Can you confirm that you are now always getting back the correct number of entries based on “limit”?

Thanks again.

I just tested this functionality again, and the issue appears to be resolved. Thanks for taking care of this so quickly.

Best Regards,
Sam Reid