1043 Posts in 379 Topics by 373 members
Page: 1 2
|Go to End||Next >|
6 May 2010 at 1:50am
I'm getting the following error on debug after upgrading to 2.4
[User Warning] Cookie 'bypassStaticCache' can't be set. The site started outputting was content at line 72 in /Applications/MAMP/htdocs/Ophoria_2.4/sapphire/dev/Debug.php
Line 33 in /Applications/MAMP/htdocs/Ophoria_2.4/sapphire/core/Cookie.php
6 May 2010 at 10:22pm
7 May 2010 at 12:55am
I'm not using the Gallery Module. I upgraded to the Latest Version of DOM just in case, but that didn't fix it. I'm still getting the error
7 May 2010 at 1:06am
same issue found when i upgrading 2.4.0. i removed gallery module and working fine for me.
another test: can you remove all old module from site and check it and let me know.
11 May 2010 at 8:27am Last edited: 11 May 2010 8:29am
I have the same problem -- after upgrading to 2.4.0, I get this error:
[User Warning] Cookie 'bypassStaticCache' can't be set. The site started outputting was content at line 63 in /srv/web/tal-15299/beta.alt-katholisch-hannover.de/mysite/code/Page.php
Cookie 'bypassStaticCache' can't be set. The site started outputting was content at line 63 in /srv/web/tal-15299/beta.alt-katholisch-hannover.de/mysite/code/Page.php
Line 33 of Cookie.php
Line 622 of Versioned.php
Line 940 of Versioned.php
Line 963 of Object.php
Line 31 of ModelAsController.php
Line 47 of ModelAsController.php
Line 111 of RootURLController.php
Line 283 of Director.php
Line 127 of Director.php
Line 127 of main.php
The only extra module installed is the blog module; I tried removing it and running /dev/build?flush=1 again, and reinstalling the blog module, but to no avail.
11 May 2010 at 11:15am
And what do you see at line 63 of your Page.php file?
It can sometimes be as simple as some forgotten text outside <?php ... ?> tags, that causes text output before cookies and other headers are set.
11 May 2010 at 9:34pm
That's what had me confused -- I looked and didn't see anything in my text editor (BBEdit on the Mac).
Then after reading your post, I tried opening it in a CLI editor, and saw that the last line with filled with junk characters that BBEdit simply didn't show in the default setting (if I turned on "Show invisibles", then BBEdit showed them). I removed that, and now it seems to work fine -- but I'm baffled as to where the junk at the end of the file came from.
Anyway, thanks for reminding me to look harder. ;-)
27 May 2010 at 11:28pm
Got same error message, but it happens everytime I install DOM.
SS2.4 - latest DOM downloaded from trunk, and right after I create some page types to use DOM, the error pops up.
Tripple checked for hidden characters, in many editors, nothing to be found there.
trace is pointing to a Object.php in mysite/code ... that file is extending dataobject..
I would be very grateful for any help ..
have a nice day.
Page: 1 2
|Go to Top||Next >|