Version 2.0 beta 2:
In User relationships the following relationship is defined as reciprocal (which I would have thought would require a confirmation from myself). However, what actually happens is that if someone decides to follow me then they receive my status updates (as expected) but I don't receive theirs' (which I guess is correct but doesn't seem to follow the reciprocal definition in the UR settings).
But then if I go to view their profile there is an unfollow button under the profile picture, which I would not expect as I didn't choose to follow them.
There are also some hangovers from v1.7 where block views are titled 'friends'.
It would be useful to retain the functionality from previous versions where friendships are mutually agreed and require confirmation - perhaps as an install option?
Alternatively, if the following route is to be followed then I would say that it should not be reciprocal and only be one way. Therefore instead of an 'unfollow' button there should be some text that says 'x is following you' or something like that.
Hope that makes sense.
Crom
| Comment | File | Size | Author |
|---|---|---|---|
| #24 | 1244998-ur-theme-2.patch | 3.28 KB | ezra-g |
Comments
Comment #1
akael commentedSubscribing, I see this also.
Comment #2
batsonjayWe've had various people notice this in the 2.0 release; I think we've whacked this issue here: #1256722: Awkward language around "following", unclosed div tag in status messages
Comment #3
gibry21 commentedThe final comment here #1256722: Awkward language around "following", unclosed div tag in status messages does not fix this issue.
Still big issues around the 'Follow' relationship.
Big enough that potentially a show stopper for me trying to sell Commons to my new employer....eeek!!
Commons 2.0 was buggy out the box and didn't seem to deliver what it promised.
The major issue still apparent here is NOT having the ability to 'Follow' somebody who has chosen to 'Follow' you. One can only select to 'Unfollow' the person despite having never chosen to 'Follow' them before.
I hope this makes sense!
Thanks
Comment #4
Crom commentedI have to agree with gibry21. I have been working with DC since v early on and can't recommend an upgrade to 2.0 at the moment because of this follow issue. However, I'm not sure if it's a bug which we can help to quosh or a design decision.
I have to say that I still don't really understand the change of relationship is it seems to conflict with the subscriptions/notifications functionality. If I want to 'follow' someone then I subscribe to them through notifications. The fact that I want to be someone's friend is a different thing altogether.
Cheers,
Crom
Comment #5
haleagar commentedStill an issue with out of the box 6.x-2.0.
and not a duplicate of http://drupal.org/node/1256722 which is related to language and conformations not the fact that two users can not mutually follow on another.
If A follows B, the following box on both A and B increments one, making the count incorrect on B's account.
In addition if user B goes to User A's page they see an Unfollow button not a follow button.
They are therefor unable to follow A.
In addition if use B clicks that unfollow it removes the A->B follow relationship which I would have assumed was "owned" by A and should not be editable by B.
If I manually create a follow request url
http://localhost/commons/relationship/[a_uid]/request/[a_uid]?destinatio...
B is able to follow A, so it is possible to follow properly, but the button used on the account page is faulty in it's detection of relationships. As is the count on the following block.
One last thing that seems "wrong" If user A follows user B a message is generated in User A's stream, but not in user B's stream. Though user B does not follow user A a notification and message in their stream seems appropriate.
I am running locally on windows XAMPP for Windows Version 1.7.3 if that helps.
this seems to be dependent on the output of _user_relationships_ui_actions_between() so this might be a issue for user_relationships, or a it may be a misuse of that function.
Comment #6
haleagar commentedcommons_profile.blocks.inc
line 108
this seems to assume that only one action will be returned, or perhaps assumes that the last action in the list will be the one that is desired. Perhaps this is inconsistent across PHP versions.
the following shows both the follow and unfollow actions.
but I'm not sure that _user_relationships_ui_actions_between can give you a single correct value.
Comment #7
gibry21 commentedJust thought I would check in on progress with this, looks like its still an issue.
I would have thought the guys at Acquia Commons would have been far more "on it" with a bug so fundamental in the functionality of a "social" network.
Really disappointing.
I am fighting with my supervisor right now.....
Her stand point:
"Open source or not.....don't release something which has such basic issues in its main functionality, doesn't inspire confidence."
I can't really argue, apart from I appreciate that open source is looked after by the community. With Commons though I guess I expected more as its a distribution that has been created and pushed by Acquia as a product that can compete with the likes of Lithium, Jive, BuddyPress....
Can it really?
Right now I don't even know where to go to get documentation or support. Acquia website has nothing but a few promotional videos, commons.acquia community....well frankly....its just a mess and I don't think anybody is even monitoring it...and the acquia sales team have no idea of the potential of the product.
Is this a deliberate ploy on Acquia's part to get people to sign up and pay for their support?? It feels like it....and if so...why not just charge for a distribution that works?!?
Sorry for the rant.....especially here....but where else can I go!!
Thanks guys.
Comment #8
lightsurge commentedMust admit I'm getting confused about subscriptions, notifications and following. Also a bit confusing that there's a daily digest function in profile settings but not ability to set notifications to go into a daily digest.
I think I'm right in saying that subscriptions are the same as notifications, and will email out posts by a user I have subscribed to as long as I have access to see those posts. So presumably posts in mutual groups and public posts, which would also go into one's stream. I'm not sure about Open groups that aren't mutual, but I'm not overly concerned about that.
Does following give me greater access to see a user's posts even if they're posted in a group I don't belong to? I wouldn't like that. And if it doesn't, I'm not sure I totally see the point of it either because it would be the same as subscriptions, except for the fact there's that public notice that I'm following this person.
I've turned off relationships in permissions, which quite neatly removes the related menu pages and follow links.
The language around relationships in the menu (i.e. 'My Relationships'!) in Commons had my first training session giggling... If this functionality sticks around, it could probably be better as something more generic! Associates, contacts, connections? I don't know if it's just a UK thing but relationships would usually spring to mind as a particular group of either family or lovers (in fact, mainly just lovers, i.e. 'We're in a relationship'), even if it doesn't exactly mean that!
Comment #9
lightsurge commentedOkay I sort of understand the digest thing now. By default Commons sends out a daily digest of activity stream occurrences. Although I've not actually seen one of these digests yet... and everything seems setup right.
Notifications/Subscriptions send out an immediate notification of new content areas subscribed to.
Comment #10
Crom commentedThis does need sorting out. I've ended up stripping out any reference to notifications and am using subscribing. User testing has backed this up as people are confused by the difference. I've also hidden much of the subs/notif functionality and given users a simpler interface rather than the default which throws everything at the user and expects them to work it out...but on the other hand that is the greatness that is drupal...just takes a while to tailor things eh!
Comment #11
Andrea C commentedSubscribing
Comment #12
selfsimilar commentedsubscribing
Comment #13
ezra-g commentedJust wanted to let folks know that this is on the top of our radar following #1298378: Identify undocumented contrib changes, which needs to be addressed so that we can update User relationships to the latest version.
We'll be sure to update this issue with the latest progress here.
Comment #14
isellakuria commentedWith regard to the count on the friends block I modified the following line in /profiles/drupal_commons/modules/features/commons_profile/commons_profile.module:
Commented line 128:
//$friends = user_relationships_load(array('user' => $account->uid, 'approved' => TRUE), array('count' => TRUE));
And inserted this line:
$friends = user_relationships_load(array('user' => $account->uid, 'requester_id' => $account->uid), array('count' => TRUE));
This way the it only counts the relationships where the current user is the requester.
However, I can't find any solution to the "unfollow" button issue, any advances in this sense?
Comment #15
delykj commentedsubscribing
Comment #16
mrryanjohnston commentedsubscribing
Comment #17
isellakuria commentedAny advances on this issue? I can help if some guidance is provided...
Comment #18
vcreatrix commentedsubscribing
Comment #19
isellakuria commentedI sent a possible temporary solution to another thread http://drupal.org/node/1307148#comment-5116830
Comment #20
ezra-g commentedThis seems to be a bug in the User relationships module: #651502: clarify reciprocal & one-way relationships .
Comment #21
ezra-g commentedComment #22
ezra-g commentedI've filed a patch against the User relationships module to fix this bug. It would be great to get some testing at that issue: http://drupal.org/node/651502#comment-5228656
Comment #23
ezra-g commentedComment #24
ezra-g commentedI exchanged screenshots with Berdir at #651502: clarify reciprocal & one-way relationships , and he helped to clarify how reciprocal relationships work in the User relationships module on a fresh install of Drupal. As a result, it seems like UR does not need the patch from #651502 applied.
However, there are some issues with the way Commons unsets everything from $user->content in hook_user() case 'view', and replaces that output with content provided by the _commons_profile_image_links_block_view() block.
A main issue is that User relationships provides several links to add and remove relationships, and commons_core iterates over the links but overwrites the value in the $links array by using the same key for each one.
The attached patch corrects this and allows links from multiple relationship types to be present and retain the ur_action class that causes them to be styled as a button by the Commons themes.
Note, this applies to the Drupal.org repository and requires an unmodified (beyond the patches in the drupal_commons.make) version of User relationships.
Comment #25
laurentc commentedRewied. Thanks.
Comment #26
ezra-g commentedThis is committed: http://drupalcode.org/project/commons.git/commitdiff/b58623f?hp=9d590073...