TYPO3 Core

Hi Thorsten,

yes. You are right. We should disable the PHP warnings, but TYPO3 gets it before a user can see it :)

We use a managed server, the provider told us to invoke the scheduler this way:
Create a new bash-file which invokes the scheduler and start this file via the cronjob

The bash-file holds these two lines:

#!/bin/bash
env -i /usr/local/bin/php5 -f /path/to/site/typo3/cli_dispatch.phpsh scheduler

Looks like it uses CLI, but to be sure could you please execute env -i /usr/local/bin/php5 -v on your server and post the result here?

(07:36:17) [~] env -i /usr/local/bin/php5 -v
PHP 5.2.13 (cgi) (built: Jan  7 2011 15:20:07)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies
    with Zend Optimizer v3.3.9, Copyright (c) 1998-2009, by Zend Technologies

Henrik Ziegenhain wrote:

[...]

PHP 5.2.13 (cgi) (built: Jan 7 2011 15:20:07)
[...]

So you're executing the CLI script using a CGI binary.

CGI is aimed to be used from a web server and TYPO3 acts like being run in a web server context.

You should ask your provider for a CLI PHP binary!

I think this could be closed.
The "bug" seems to be caused by a wrong configured system.

Thorsten Kahler wrote:

First step: disable PHP warnings on production sites ;-)

btw: whats the preferred way to disable PHP warnings? Via php.ini (display_errors = off) or via the TYPO3 Install Toll (increase [SYS][systemLogLevel] to 3 or higher)

Thanks for your support!