I'm running 4.7.2 and installed this module to work with a master and 4 slaves, everything seems to be working fine, except on the master it sometimes displays the following error:

warning: Cannot modify header information - headers already sent by (output started at /home/drupal/includes/bootstrap.inc:546) in /home/drupal/includes/common.inc on line 139.

Comments

danielc’s picture

danielc commented

Seems like you are using caching. Is that correct?

A way to quickly resolve this issue doesn't hit me right now. I don't have the time to look into it. You or someone else needs to come up with a patch for singlesignon and/or Drupal to fix this.

Ariadoss’s picture

Ariadoss commented

Sorry, it seems this error was being caused by robotstxt.module, my apologies. Though I didn't receive this error until I installed single sign-on. =P

bxy’s picture

bxy commented

i second the bug report.

i am not running single-sign on. I am running drupal on ubuntu 6.06 lamp server.

all my 5 drupal-4.7.2 powered sites had this error msg (seems like whenever a anonymous visitor hits the site, a error occured):

Type php
Date Monday, August 7, 2006 - 04:13
User anoymous
Location http://blog.fltrp.com/fayu/?q=user/67/track
Referrer
Message Cannot modify header information - headers already sent by (output started at /var/www/fayu/includes/bootstrap.inc:546) in /var/www/fayu/includes/common.inc on line 139.
Severity error

danielc’s picture

danielc commented

Ariadoss: how did you narrow it down to robotstxt.module?

bxy: do you also have robotstxt.module installed?

Ariadoss’s picture

Ariadoss commented

Sorry, I made another mistake it is still occurring, even though I disabled robotstxt.module, it is only caused by anonymous users as reported earlier. I'll try to disable and enable modules again to better narrow it down.

Ariadoss’s picture

Ariadoss commented

Again, it occurs only with anonymous users or when you first login, I don't think it's the signle sign-on anymore, I'm sorry for my mistake, but I'll try to figure out what's causing it tonight. Thanks for the help.

Ariadoss’s picture

Ariadoss commented

Oh for further details, it occurs on any page accessed by anons and I also running Drupal for multiple websites. Sorry, for the repeated posts, there doesn't seem to be an edit post option here.

Ariadoss’s picture

Ariadoss commented

It seems in my case singlesignon *is* causing the error. I disabled it, and was not able to encounter the same error again. Once, I re-enabled it the error showed up immediately. Sorry for all the trouble but it turns out my first assumption was correct. Any, ideas now on what is causing this aside from the caching? Thanks. :)

zis’s picture

zis commented

I'm getting the same error.. I have singlesignon and caching enabled.. when i disable either one of them the error disappears..

danielc’s picture

danielc commented
Status: Active » Closed (fixed)

No one has pointed to anything particular in singlesignon.

kdes’s picture

kdes commented
Status: Closed (fixed) » Active

was this problem fixed ?

duaelfr’s picture

duaelfr
he/him
Primary language French
Location Montpellier, France
commented
Status: Active » Closed (won't fix)

This version of Shared Sign-On is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.