Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.okay. so admin can view all the statuses made and their own. but, authorized users cannot see any statuses or their own.
for instance... if you log on as an auth user, and go to the block that shows recent status updates, all you will see is usernames with an N/A besides them.
however, auth users can make a status update. they just cant see it.
permissions are as follows:
edit all statuses
edit own status X
post on all profiles X
use open API X
view all statuses X
I attached a pic of the fbss block.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | ss2.JPG | 17.85 KB | jrpowell01 |
| #5 | ss.JPG | 9.83 KB | jrpowell01 |
| ss.JPG | 8.88 KB | jrpowell01 |
Comments
Comment #1
icecreamyou commentedNo file in FBSS contains the text "n/a," nor does FBSS reference any external function that contains the text "n/a" as far as I can find, and I can't reproduce your problem (nor, apparently, can the other thousands of FBSS users). So what you're seeing is probably the result of a bad upgrade, permissions needing rebuilding, or some modification of the code. I suggest you delete the facebook_status folder, replace it with the latest dev, run update.php, and then refresh your browser cache. If it's still not working, rebuild your permissions.
Also check and see if the statuses get saved in the database (PHP version and SQL version and type are always good details to include).
Comment #2
jrpowell01 commentedokay. im going to give it a try right now.
Comment #3
jrpowell01 commentedokay i got nothing new except the the 'save' button is now in the correct spot. authorized users still get N/A in place of what should be their or another persons status.
Comment #4
jrpowell01 commentedstill works fine for admin. and how do i rebuild permissions?
Comment #5
jrpowell01 commentedComment #6
jrpowell01 commentedwow. this is bs... rebuilt permissions and non-admin users still get the same old thing... N/A where their status should be. are their any modules that could be conflicting with fbss? ?
Comment #7
icecreamyou commentedGo to admin/content/node-settings and click the Rebuild Permissions button.
Also check your database and see what shows up in the facebook_status table and let me know what version of PHP and what type and version of SQL you have.
If rebuilding permissions doesn't work, try giving authenticated users the Edit All Statuses permission and see if that does it. There was a bug awhile back that kept users on some systems from posting new statuses without that permission and I suppose this could be related.
Comment #8
jrpowell01 commentedwell i rebuilt permission but i dont know check my database. but i will try giving them edit all.
Comment #9
icecreamyou commentedFor my sanity, please try not to post 5 comments in rapid succession. If you're in need of feedback that quickly, try the #drupal channel on IRC.
Also, I just looked it up, and this is unrelated to the other bug I mentioned. The problem is probably related to the input filter that you're running over the statuses having too high permissions.
Comment #10
icecreamyou commentedAlright, I can reproduce the issue. You need to go to admin/settings/facebook_status and set the "Input filter" option to something that your authenticated users can see. (FYI, check_markup() is where the "n/a" is coming from.)
Comment #11
jrpowell01 commentedwoohoo! thanks ice! that was too easy of a fix for this much frustration. i actually forgot all about changing the my input filter... thanks you!
Comment #12
jrpowell01 commentedfixed! :)