Closed (fixed)
Project:
Advanced Profile Kit
Version:
5.x-1.0-alpha5
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2008 at 14:46 UTC
Updated:
14 Jul 2012 at 19:36 UTC
When I put my buddy list up, no matter which profile is currently being viewed, the buddylist for the user that is currently signed in is displayed.
So, if I sign in as user XXX, and then go to look at the profile of user YYY, YYY's buddylist will display the buddies of XXX (it should be showing YYY's buddies).
What is the best way to get it to show the correct buddies?
Thanks!
Comments
Comment #1
jackspiv commentedLooks like I've got the same problem
FWIW, my config.
Drupal 5.7
Configuration file Protected
Cron maintenance tasks Last run 1 week 4 days ago
You can run cron manually.
Database schema Up to date
File system Writable (public download method)
JQuery Update Installed correctly
The current installed version of JQuery is 1.1.2
MySQL database 4.1.14
Organic groups modules Organic groups works best when job_queue.module.module is enabled. See the Integration section of the README file.
PHP 5.0.4
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Web server Apache/2.0.54 (Fedora)
Comment #2
jackspiv commentedAn update ...
FWIW
For me, this problem resolved itself when I switched back to buddylist from buddylist2. As michelle has pointed out, APK doesnt support buddylist2.
no problem now.
also, going backwards is (only a little) challenging ...
Uninstalling Buddylist2 would presumably remove the buddylist tables from the database.
So I exported them first from the database before uninstalling.
then uninstalled buddylist2 and reinstalled buddylist.
this created two empty buddylist tables.
I then imported the buddylist table files that I had exported back into the database.
Surprisingly enough everything worked beautifully.
Now everyone has buddies again. What a wonderful world.
Comment #3
michelleYep, just buddylist 1.
Michelle
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.