#482 Warning: session_start(): Cannot send session cache limiter

[Anonymous]

Hi all,
i started and moved mrbs to webserver from "1und1. copied my prepared mrbs from local host while changing db names in config.php.inc. Intially it worked ok, until I noticed that I need to change the title "room booking system" to a differnt word. Did so in Lang.de and moved this via FTP. until than I got an error message:

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /homepages/x/xxxxxxx/htdocs/xxxxxxxxxx/mrbs/lang/lang.de:1) in /homepages/x/xxxxxxx/htdocs/xxxxxx/mrbs/session/session_php.inc on line 53

Warning: Cannot modify header information - headers already sent by (output started at /homepages/x/xxxxxxx/htdocs/xxxxxxxxxx/mrbs/lang/lang.de:1) in /homepages/x/xxxxxxx/htdocs/xxxxxx/mrbs/index.php on line 27

I deleted and copied new files but did not help.
I is called from a Joomla controlled website.

Can you help ?
thanks, Horst

[Campbell Morrison]

If it worked before then you just need to get back to the files you had before (easier said than done sometimes of course). I suspect the problem is that the editing process introduced some typos which are causing the error.

By the way, if you are using 1.4.10 then a better way of changing language strings is to use the $vocab_override feature in the config file, instead of changing lang.de. For example in your case put

$vocab_override['de']['mrbs'] = "Your new description";

That way you won't have to re-apply your changes when you upgrade to a new version of MRBS.

Campbell

[Anonymous]

Thanks Campbell, I think I tried to bring in the olde version of what I had, still have the error. So, you think it is just a typo error somewhere made? I looked for one and did not find anything in my changes. As I am not an php expert nor a joomla one, i thought that some type of conflict how I made it happen is the cause. I will review all the files I have changed and see if there is anything strange in it. Thanks anyway.
Horst

[Campbell Morrison]

Sometimes you get this problem if you've accidentally inserted some whitespace after the closing ?> at the end of a PHP file. (In the latest versions in the trunk the closing ?> tags have been removed because they are not necessary and cause problems such as this, but in 1.4.10 they are still there.)

Campbell

[Anonymous]

I redid everything today carefully and it's back to work. Thank you.

Horst