Closed (works as designed)
Project:
Facebook-style Statuses (Microblog)
Version:
5.x-1.0-rc2
Component:
Code - Functionality
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Mar 2009 at 14:38 UTC
Updated:
28 Mar 2009 at 03:18 UTC
Comments
Comment #1
icecreamyou commentedIt is the intended behavior of the module, as explicitly explained in the documentation, that the Facebook Status block follows these rules:
1. On user profiles, it displays the relevant user's status;
2. On nodes, it displays the node author's status;
3. Anywhere else, it displays the current user's status.
If you want the block to always show the current user's status, create a new block with the PHP input format and put this in it:
5.x:
6.x:
Comment #2
barrett commentedI see that the solution given for 6.x does work, but I have no idea why it does. Putting the same code into a new block type defined inside the module results in the default handling (i.e., the user displayed varies by what you're viewing). Can someone enlighten me?
Comment #3
icecreamyou commentedIt's not the same code that's in the module. It's intentionally different so it gives a different result.
In the 2.x branch admin can choose whether to enable this kind of behavior ("Legacy") or just have the block consistently display the current user's status like the code above does.
Comment #4
barrett commentedYeah, I meant that it doesn't work even when I put that code into the module as a new block. For instance, in the code below I define the new block and set its view op to call facebook_status_display_b() passing the $user->uid as the id but I still get the default/"Legacy" behavior.
Comment #5
icecreamyou commentedNever modify the module file unless you absolutely have to.