Breaking News: Facebook Page Bug – These Will Impact Your School or Company Page
I wanted to share Facebook’s newest change, one that is only a few hours old and a surprise to all – Such a surprise that I currently have come across only one article explaining these changes.
Just a few hours ago Facebook rolled out a new privacy setting that is going to seriously impact Facebook page administrators and the ability to respond to comments posted by fans of the page. If a commenter has their privacy settings set to allow “just friends” to comment on their posts then a page administrator will not be able to reply to a comment left on the wall. This can only be changed by the specific user. Facebook users can change this by changing their privacy settings to allow everyone to comment on their posts:
How to Change Privacy Settings:
>Account, >Privacy Settings, >Customize Settings, and under “Things I Share” make sure “Can Comment on Posts” is changed to “Everyone”
There also seems to be a glitch on some of the pages I am an administrator for. As a page administrator, I can post status updates coming from the school/company Facebook page, but when I go to comment on another post it replies from my personal account:
Status update from page administrator:
When I respond to a post on Facebook as a page administrator it shows up from my personal account, not from Effective Student Marketing:
Since our team here at Effective Student Marketing just learned about this change, we are working on different strategic options on how to handle this. For now, I would recommend a status update on your school/company Facebook page explaining these changes and informing the people that “like” your page on how they can change their settings.
UPDATE:
1. Facebook has acknowledged the issue here, meaning it is more than likely a bug on the site. Facebook is working on fixing the problem, so here is a suggestion in the meantime: If your school/company Facebook page is affected by this, change the settings on your page so that people cannot post or comment and create a note explaining the issue. Users can comment on notes still, so this will work temporarily.
2. The bug is officially fixed! Thank goodness!
