Error: Cannot modify header information. Theme conflict?

Resolved Monoloid
(@monoloid)

11 years ago

Hi,
I get this error:

Warning: Cannot modify header information – headers already sent by (output started at /home/………../wp-content/themes/Gameleon/front-page.php:15) in /home/………./wp-includes/pluggable.php on line 1178

I’m redirecting the custom login-page to the standard BuddyPress login-page.

I’m using the Gameleon theme. http://www.tiguandesign.com/demos/Gameleon/magazine/

I first got this error on another website I’m working on, but set up a new page just to test this with only the plugins Buddypress and My Private Site. I still get the same error when I turn off Buddypress so can this be a conflict with the theme?

https://wordpress.org/plugins/jonradio-private-site/

Viewing 15 replies - 1 through 15 (of 18 total)

1 2 →

Thread Starter Monoloid
(@monoloid)

11 years ago

I don’t get this error when I use other plugins that do the same as My Private Site. I can’t use any of those since this one is the only one I’ve found that has the option to whitelist more than one page.

Thread Starter Monoloid
(@monoloid)

11 years ago

Resolved it! Had to remove the whitespace between “?>”
and “<?php” (line 14) in the front-page.php of the theme.

Plugin Author David Gewirtz
(@dgewirtz)

11 years ago

Awesome!

sowp
(@epigeneration)

10 years, 11 months ago

hi there, i’m getting a similar error message – but unfortunately i’m not so advanced as monoloid.

here is the error message i get:
Warning: Cannot modify header information – headers already sent by (output started at /home/…./wp-content/themes/klein/buddypress.php:9) in /home/…./wp-includes/pluggable.php on line 1196

any of you know what i have to do? what and were was the “whitespace” you mentionned?

sowp
(@epigeneration)

10 years, 11 months ago

i tried to take of space on the line 9 as mentioned on the error message but nothing changes. i get directed to the activate page of my site with the request to enter an activation key… never happened before using My Private Site.

btw, i also chose to “Omit ?redirect_to= from URL (this option is recommended for Custom Login pages)” in the hope nothing different would happen then what i had before…

Thread Starter Monoloid
(@monoloid)

10 years, 11 months ago

Open the “buddypress.php” file and remove whitespace after ?> (or any other code) in line 9 (or 10).

Thread Starter Monoloid
(@monoloid)

10 years, 11 months ago

Do you mean that after removing the whitespace you get redirected to the activation page? Or do you get the exact same error?

sowp
(@epigeneration)

10 years, 11 months ago

8
9<?php get_header(klein_header()); ?>
10

above is what i see on line 8-10.

to you second question: i get the error message the first time i open click on the activation link sent per email. if i refresh or click on the same link again (in the same browser) i get this request to enter an activation key.

shall i try to delete the space between ; and ?> and re-register from scratch?

Thread Starter Monoloid
(@monoloid)

10 years, 11 months ago

Try deleting the space after ?> on line 9 and till the next code. I guess that means deleting line 10. It will then probably look something like this:

9<?php get_header(klein_header()); ?>
10<?…….

PS: I’ll be off for a few hours now. Need some sleep.

sowp
(@epigeneration)

10 years, 11 months ago

good morning 🙂
had to crash, too!
firstly for you help!! so i did what you just proposed and it didn’t work – unfortunately. the error still comes up after a new full registration.
i disabled My Private Site and it works. it seems to be a problem between buddypress, pmpro and the MPS plugin… maybe also with the theme but not convinced as i saw many having the same issue than me (about the activation part at least) with buddypress and plugins with effect at registration/activation with redirect function.
looking forward to david’s opinion.

sowp
(@epigeneration)

10 years, 11 months ago

*thanks(!) 🙂

Thread Starter Monoloid
(@monoloid)

10 years, 11 months ago

Can you try this:

9<?php
10get_header(klein_header());
11?>

This means removing the two whitespaces in that line.

PS: I’m not an expert on this – I just look for solutions online and then fool around with the codes until it works… 😛

Plugin Author David Gewirtz
(@dgewirtz)

10 years, 11 months ago

I’ll take a look at it today. Stay tuned!

–David

P.S. Switching post status to not-resolved.

Plugin Author David Gewirtz
(@dgewirtz)

10 years, 11 months ago

Okay, I’ve gone ahead and set up a very basic system, with a completely refreshed database, Twenty Thirteen as my theme, My Private Site, BuddyPress, and PMPro all activated. I did the most basic settings I could for each, and I’m seeing no error messages.

So that’s at the most basic level.

But I am a bit confused, since it seems that something like PMPro and My Private Site might be attempting to do the same thing: regulate access. I haven’t tested them extensively (frankly, this was the first time I’ve loaded PMPro), but I’d really need to understand better when you expect MPS to run with the ball and when you expect PMPro to do the deed.

It does seem to me you have a lot of balls in the air at once, and it’s going to be necessary to think through each of these things. BuddyPress adds tons of profile and social capabilities, but so, in some way, does the membership plugin. The membership plugin controls access to certain areas of the site, but so does BuddyPress in terms of groups, and so does My Private Site, in terms of URL blocks. And that doesn’t even begin to take into account anything with the theme.

When I get this funky on one of my sites, and run into a problem like you did, I spin up a test site, and carefully add in new components and elements, adding and removing and testing until I can see what’s going on. I find it’s the only way to get a good handle on things.

That’s sort of what I did with you, tonight. Since I’d never tested BuddyPress, My Private Site and PMPro together, I wanted to see what would happen if I turned them all on in a fresh environment. When nothing blew up, it became at least basically clear that in their most default incarnations, they’re not eating each others’ tails.

But as you spin up a test site and start adding in and pulling out complexity, you’ll get a better feel for what is interacting with what. If you can narrow it down so it’s repeatable, I’ll be happy to look at code fixes. But my guess is it’s something in the mix and you’ll need to find out what that is before anything else can be done.

–David

sowp
(@epigeneration)

10 years, 11 months ago

hi monoloid and david!
thanks for doing this, david. it’s actually what i did yesterday but with my own site running. for some undefined reason, my site works fine without MPS and with instead buddypress members only plugin. it basically does the same as MPS but in much simpler way.
the reason i need an additional plugin aside of PMPro is that for some reason the developer didn’t want to have or adjust for the restriction functionality of buddy press’s typical pages like activity and members… i saw on the web that he gave the coding to sort it out but i got no idea were to put it.
so, i hope the rest will be fine but with BPMO at least i got all closed for people that didn’t logged in – which is fine for me cuz the first membership level i have is for free anyhow.
at this point of my organisation it doesn’t make sense for me to pay for PMPro support (which costs almost 100$) but hopefully later.
this is just a middle term fix and hopefully it will continue to work out this way without problems… i’m very conservative with my additions of plugin but this one is key for me for now 🙂
so thanks anyhow! in case you want to dig into this further, i’m using a premium theme called klein, which was developed for buddypress functions.
cheers,
s