Posting to remote group doesn't always work
Posting to remote group doesn't always work
| Issue ID: | 3507 |
| Issue Category: | bug |
| Component: | groups |
| Priority: | normal |
| Status: | active |
| Assigned: | mymmn |
| Version: | 1.0 |
| Milestone: | 1.0 |
| Keywords: | patch exists |
Some groups that I'm remotely subscribed to, don't receive posts directed at them. In fact, the group tag doesn't even linkify.
Using this as a perfect example
http://micro.thelovebug.org/notice/73
At the time I posted this, I was already a member of the !statusnet, !identiverse and !tzag groups on identi.ca from my own instance. However, although the !statusnet post seems to have gone through, the other two have not.
I have tried posting again today:
http://micro.thelovebug.org/notice/217
And still no joy.
I have recently been experiencing problems remotely subscribing to groups that reside on identi.ca, in some cases attempting up to 30 times to subscribe, and I also don't get avatars of those groups. To be clear, I do get avatars when remotely subscribing to groups on /other/ statusnet instances.

Updates
#1
It appears this is part of the problem:
http://micro.thelovebug.org/notice/355 was posted to the tzag group using the web interface. That's why the '!tzag' doesn't wind up being a link.
When I look at http://identi.ca/group/tzag, this dent is definitely there. No one in that conversation has used the !tzag tag to put it there, so the initial post must have done it.
As far as the other examples, I've definitely seen posts fail to push to Identi.ca from my instance but I think it's the general instability lately and not a bug.
I am not an expert, however.
#2
The only reason that dent ended up in the tzag group is because I explicitly selected it from the drop down menu under my status message. At least 3 prior attempts, just using the !tzag tag, failed. e.g. http://micro.thelovebug.org/notice/217
Other group postings, like http://micro.thelovebug.org/notice/73, partially worked.
#3
A follow up to this:
Posts to !feds don't work under normal circumstances, using the !feds group tag only. However, if I put a row in my local group_alias table for feds with the same group_id as in user_groups, and then try and post to !feds, it works!
It's almost as though StatusNet is unable to ascertain the group_id from the user_groups table on its own.
#4
I think there (in some cases) is another problem than the group not existing in group_alias.
If you look at classes/User_group.php on line 412 in the current code, you can see that a call to
$profile->getGroups()is made. This implies $limit=PROFILES_PER_PAGE only giving (in my case 20) groups.This means only the first 20 groups in an ascending numerical order by locally stored User_group->id will be addressable with the bangtag syntax.
I solved this by making the call on the line previously mentioned to:
$profile->getGroups(0, null);as it's used in Profile->isMember().#5
Merge request is at https://gitorious.org/statusnet/mainline/merge_requests/204
#6
You can also subscribe to the
RSS feed for updates to this issue.