I have installed all the necessary modules for buddylist2. I completed the tasks under site management and users to enable the program. If you look at the site you will see the invite a friend and my buddy list. I've sent out an invite and it was received. The friend accepted the invitation and registered on the web site. When I look at my buddy list their name does not appear either under my buddies or under pending requests, I'm not sure what I am missing. The site is at http://www.makingbigmedicine.com

Any suggestions would be appreciated.

Lori

Comments

nodestroy’s picture

nodestroy commented

Hi,

i have registered, and invited a second user (bigair) - and it works.
to test the listing of your user, i requested to add you to buddylist, and you are shown under "send requests".

that means, everything should be ok ;)
please test again, and report

regards,
dominik

webdzyner’s picture

webdzyner commented

Thanks Dominik. Not sure what happened with Sally but everything else seems to be working great. Thanks for the look. :-)

nodestroy’s picture

nodestroy commented
Status: Active » Fixed

ok, sounds fine ;)

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

sylv3st3r’s picture

sylv3st3r commented
Version: 5.x-1.x-dev » 5.x-1.0-beta1
Component: Buddy API Invite » Buddy API
Status: Closed (fixed) » Fixed

Sorry to bring this up again. But I seem to figure out what's the cause. Actually it's not buddylist2 fault. It's usernode. Problem is with usernode, users who have been added prior usernode installation didn't have any usernode. So whoever have this problem, there's a fix already on usernode. Update to usernode 5.x-1.4. There's a fix : #258040 patch by alfaguru: Fixed possible issues when not all users have usernodes due to database inconsistencies. Righto, just so any other who have similar problems know it.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.