Error messages with v2.64

4 posts by 2 authors in: Forums > CMS Builder
Last Post: March 12, 2015   (RSS)

By Dave - March 11, 2015

Hi Deborah, 

Great feedback, thanks!  And so glad to hear you love the new error reporting feature, we do too! :-)

For this warning: "session_start(): Cannot send session cache limiter - headers already sent", that's from the backup function.  You can safely hide that warning by adding a @ on line 762 as follows:

  @session_start();

And I've update that in the next beta release as well.

And for the cPanel error "syntax error, unexpected '"' ", you can just comment this line with a leading ; like this:

;date.default_longitude "CMSB_CONFIG_USER_INI"

Lastly, .user.ini is a new config file we added and we used the # style comments, and some PHP versions have a problem with those.  So if you get any errors feel free to replace # with ; which is another way of commenting a line in php.ini and .user.ini config files.  And that's safe to ignore as well if you're not getting any errors, it will be updated in the next release as well.

Great feedback, let me know if I can provide any more info on any of that or if you spot anything else.  Cheers!

Dave Edis - Senior Developer
interactivetools.com

By Dave - March 11, 2015

Hi Deborah, 

Great feedback, thanks!  And so glad to hear you love the new error reporting feature, we do too! :-)

For this warning: "session_start(): Cannot send session cache limiter - headers already sent", that's from the backup function.  You can safely hide that warning by adding a @ on line 762 as follows:

  @session_start();

And I've update that in the next beta release as well.

And for the cPanel error "syntax error, unexpected '"' ", you can just comment this line with a leading ; like this:

;date.default_longitude "CMSB_CONFIG_USER_INI"

Lastly, .user.ini is a new config file we added and we used the # style comments, and some PHP versions have a problem with those.  So if you get any errors feel free to replace # with ; which is another way of commenting a line in php.ini and .user.ini config files.  And that's safe to ignore as well if you're not getting any errors, it will be updated in the next release as well.

Great feedback, let me know if I can provide any more info on any of that or if you spot anything else.  Cheers!

Dave Edis - Senior Developer
interactivetools.com

By Deborah - March 12, 2015

Dave, No more errors! I replaced all leading # comments with the semi-colon in the .ini file.

Thanks.
~ Deborah