37 pointsStarting to get into this DEV thingI'm new here
craniumstudio
Member
—
16th January 2012 (4 months ago)
Under "Theme Settings" -> "Buddypress Settings" -> "Users Privacy Setting"
I have it enabled and have inserted a link for the user to go to.
When a user clicks on a non-friend name under the members list they get the error below. When they click on friend everything works well.
Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/public_html/dev001/wp-content/themes/bp-social/members/single/home.php:12) in /home/mysite/public_html/dev001/wp-includes/pluggable.php on line 866
I have tried removing all plugins with no success, I have also tried a fresh install and still get the same result.
Under "Theme Settings" -> "Buddypress Settings" -> "Users Privacy Setting"
I have it enabled and have inserted a link for the user to go to.
When a user clicks on a non-friend name under the members list they get the error below. When they click on friend everything works well.
Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/public_html/dev001/wp-content/themes/bp-social/members/single/home.php:12) in /home/mysite/public_html/dev001/wp-includes/pluggable.php on line 866
I have tried removing all plugins with no success, I have also tried a fresh install and still get the same result.
Responses (4)
Sales & Support Pro — 16th January 2012 (4 months ago) #
Hiya!
Yes, I also get this in my tests. Let me pass this onto the developer for a fix.
Thanks,
Phil
Geeky Developer — 21st January 2012 (4 months ago) #
hi
could you try the same fix method on this thread
http://premium.wpmudev.org/forums/topic/social-theme-bug
let me know if it fix this issue ok.
Member — 21st January 2012 (4 months ago) #
Hi Richie,
Thanks. I tried the fix you mentioned above and got the same error.
I was thinking about applying this method: http://wpmu.org/how-to-add-profile-privacy-to-buddypress/
Do you think this will work?
Member — 31st January 2012 (3 months ago) #
The update 1.3.3 seems to have fixed the issue.
Thanks Richie
Become a member