Favorites webpage vs. API calls inconsistency

Favorites webpage vs. API calls inconsistency

Issue ID:3649
Issue Category:bug
Component:api
Priority:normal
Status:active
Assigned:Unassigned
Version:1.0
Milestone:1.0
Keywords:api, favorites, webui

When TwitterBridge imports a repeated notice, StatusNet stores it twice: first is the "original", second the repeated one.

When trying to mark it as favorite with Seesmic mobile client, Seesmic uses the repeated id (ie the second one).
But, when building favorites web page, StatusNet uses the first id, with 'repeated by XXX' mention.

Thus, notice is showed as not faved

Updates

#1

Fix has been submitted as merge request:
https://gitorious.org/statusnet/mainline/merge_requests/2236

Login or Register to modify this issue, or to receive updates by email.

You can also subscribe to the RSS feed for updates to this issue.