Closed (fixed)
Project:
Facebook-style Statuses (Microblog)
Version:
6.x-2.x-dev
Component:
Code - Functionality
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2009 at 10:39 UTC
Updated:
2 Aug 2010 at 15:30 UTC
Comments
Comment #1
icecreamyou commentedFirst make sure you really did set the permissions correctly. If you were upgrading, make sure you deleted the entire facebook_status folder before upgrading and completely cleared the cache afterwards. Then check /admin/settings/facebook_status and make sure you're not running a filter over the statuses that non-admin can't use. You may also need to click the "Rebuild permissions" button at /admin/content/node-settings.
Comment #2
portait commentedArrgh... the problem was the filter. Thank you so much for helping. :)
Comment #3
icecreamyou commentedNo problem, glad it works.
Comment #5
TonyK commentedI've encountered the same issue some time ago. I think there should be filter access check only for users who are editing statuses (not viewing). As said in the doumentation:
Note that this will check the permissions of the current user, so you should specify $check = FALSE when viewing other people's content.
Comment #6
icecreamyou commentedTrue actually. Thanks, should be fixed in dev.
The reason I had it that way before is that we actually don't check access on add/edit. This is because there's no selection of filters on the status update form, it's just assigned in the administrative settings. So in addition to this change, I increased the forcefulness of the warning on the admin settings page that choosing a loose filter could be a security risk.