PARTY FOUL: I was unintentionally reverting to pre 1.0b1 versions of the files. Thus the bugs. Thus my insanity for swearing up and down that I was using the original code. I was… just *too* original.
Is this a database cache problem? How does one fix that? (Note: this is *not* a browser caching issue. I’ve tried loading the page on different browsers on different machines on different operating systems)
Note: This “touching” problem does not seem to affect my test server. The test server is running PHP 5 whereas the “problem” server is PHP 4? Do people know what I mean when I say “touching” or am I coming across as a weirdo?
Haha. That’s the truth. It’s a shame for the people trying to play in my neighborhood.
Yeah, I changed it to default to active… or at least, that’s how I wanted to change it. get_newest_users, get_active_users and get_popular_users all do not work properly with bp-core-widgets.php. They *do* work in bp-core-directory-members.php. What’s the difference between those pages?
I removed the Google Analytics; same results. Then I remembered that I removed the members widget JavaScript file because of a weird bug I was getting: when one clicked on “newest”, *every* member loaded in the page. For even moderate member rosters this can kill a browser. I’ve re-activated that Javascript. The two “blank” members are still there, but, funny thing: now if you click on any of the sort links (eg “newest” “active” “popular”) the proper members are displayed. The silver lining is that I am no longer seeing that first bug where all members were loaded in the page.
Narrowing the problem: I see that the $users array has 0 members. What could cause that? This line isn’t getting the users it should:
