TYPO3 Mailingliste: nicht fragen - lesen!

Hi,

Typo3 4.0.6

The back end went blank again today. Again, manually deleting the
temp_CACHED_* files in typo3conf/ brought it back. I checked the
typo3conf/localconf.php file and noticed the last change was made on
5/23/2007. I've seen the problem twice in the past couple of years. Can
anybody shed some light on what might be going on? How and why
temp_CACHED_* files prevent back end from showing up?

Thanks in advance,

Bing
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi,

We have a similar problem a two moths ago in typo 4.1 , BE went blank
instead to show a error message when we have a error in the code. But
we have

We resolved this setting $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1'
in localconf.php.

Regards.

Iván Gómez Rodríguez
Ingeniero en Informática
mailto:igomez (AT) igalia (DOT) com
Telf: +34 986 10 76 10
Fax: +34 981 91 39 49
Igalia http://www.igalia.com


Bing Du wrote:
> Hi,
>
> Typo3 4.0.6
>
> The back end went blank again today. Again, manually deleting the
> temp_CACHED_* files in typo3conf/ brought it back. I checked the
> typo3conf/localconf.php file and noticed the last change was made on
> 5/23/2007. I've seen the problem twice in the past couple of years. Can
> anybody shed some light on what might be going on? How and why
> temp_CACHED_* files prevent back end from showing up?
>
> Thanks in advance,
>
> Bing
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english (AT) lists (DOT) netfielders.de
> http://lists.netfielders.de/cgi-bin/.../typo3-english
>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Am Thu, 07 Jun 2007 10:29:17 -0500 schrieb Bing Du:

> Hi,
>
> Typo3 4.0.6
>
> The back end went blank again today. Again, manually deleting the
> temp_CACHED_* files in typo3conf/ brought it back. I checked the
> typo3conf/localconf.php file and noticed the last change was made on
> 5/23/2007. I've seen the problem twice in the past couple of years. Can
> anybody shed some light on what might be going on? How and why
> temp_CACHED_* files prevent back end from showing up?
>
> Thanks in advance,
>
> Bing


Hi Bing,

the temp_CACHED_* files include the extensions. You see a blank backend
typically during updates, if dependencies between extensions are out of
order. Files, functions or objects are requested by extensions but
not have been loaded in the right order and the whole PHP processing breaks.

That starts the circulus vitiosus. You can't delete the temp_CACHED_* files
with the green clear cache buttons any more, because the button itself
doesn't show up because of the blank pate.

The cause for missing dependencies seems to be a bug in the extension
upload tool, wich often looses the dependences during upload for
mysterious reasons I can't figure out.

Until that has been fixed by the core team, you will probably see a blank
backend now and then upon updates and you have to order the extension keys
manually with an text editor.

Not a solution for everybody. Yeah, that's why they proudly call TYPO3 an
expert system ;-)



Regards

Elmar
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

> Bing Du wrote:
>> Hi,
>>
>> Typo3 4.0.6
>>
>> The back end went blank again today. Again, manually deleting the
>> temp_CACHED_* files in typo3conf/ brought it back. I checked the
>> typo3conf/localconf.php file and noticed the last change was made on
>> 5/23/2007. I've seen the problem twice in the past couple of years. Can
>> anybody shed some light on what might be going on? How and why
>> temp_CACHED_* files prevent back end from showing up?
>>
>> Thanks in advance,
>>
>> Bing
>>
> Hi,
>
> We have a similar problem a two moths ago in typo 4.1 , BE went blank
> instead to show a error message when we have a error in the code. But
> we have
>
> We resolved this setting $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1'
> in localconf.php.
>
> Regards.
>
> Iván Gómez Rodríguez
> Ingeniero en Informática
> mailto:igomez (AT) igalia (DOT) com
> Telf: +34 986 10 76 10
> Fax: +34 981 91 39 49
> Igalia http://www.igalia.com
>
>

That's a good hint. Thanks. Besides showing the error right up front on
the page, were you also able to find it in any logs, say Apache error log
file? My concern with showing error message on the page is it could
reveal system config or file structure information. This time, since I
already deleted temp_CACHED_* files and the back end came back up, I was
not able to catch the error on the page. I'll try it next time.

Bing
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

> Am Thu, 07 Jun 2007 10:29:17 -0500 schrieb Bing Du:
>
>> Hi,
>>
>> Typo3 4.0.6
>>
>> The back end went blank again today. Again, manually deleting the
>> temp_CACHED_* files in typo3conf/ brought it back. I checked the
>> typo3conf/localconf.php file and noticed the last change was made on
>> 5/23/2007. I've seen the problem twice in the past couple of years. Can
>> anybody shed some light on what might be going on? How and why
>> temp_CACHED_* files prevent back end from showing up?
>>
>> Thanks in advance,
>>
>> Bing
>
>
> Hi Bing,
>
> the temp_CACHED_* files include the extensions. You see a blank backend
> typically during updates, if dependencies between extensions are out of
> order. Files, functions or objects are requested by extensions but
> not have been loaded in the right order and the whole PHP processing
> breaks.
>
> That starts the circulus vitiosus. You can't delete the temp_CACHED_*
> files
> with the green clear cache buttons any more, because the button itself
> doesn't show up because of the blank pate.
>
> The cause for missing dependencies seems to be a bug in the extension
> upload tool, wich often looses the dependences during upload for
> mysterious reasons I can't figure out.
>
> Until that has been fixed by the core team, you will probably see a blank
> backend now and then upon updates and you have to order the extension keys
> manually with an text editor.
>
> Not a solution for everybody. Yeah, that's why they proudly call TYPO3 an
> expert system ;-)
>
>
>
> Regards
>
> Elmar

Thanks much for your explanation, Elmar. What you said makes sense. We
ever run into blank screen due to extension installation. But this time,
it didn't seem to be extension related. There was no new extension
installed and no extension was updated either. Other than usual content
editing, Tool->Log doesn't show any system level operations over the past
several days. Hm.

Bing

_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

>> Bing Du wrote:
>>> Hi,
>>>
>>> Typo3 4.0.6
>>>
>>> The back end went blank again today. Again, manually deleting the
>>> temp_CACHED_* files in typo3conf/ brought it back. I checked the
>>> typo3conf/localconf.php file and noticed the last change was made on
>>> 5/23/2007. I've seen the problem twice in the past couple of years.
>>> Can
>>> anybody shed some light on what might be going on? How and why
>>> temp_CACHED_* files prevent back end from showing up?
>>>
>>> Thanks in advance,
>>>
>>> Bing
>>>
>> Hi,
>>
>> We have a similar problem a two moths ago in typo 4.1 , BE went blank
>> instead to show a error message when we have a error in the code. But
>> we have
>>
>> We resolved this setting $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1'
>> in localconf.php.
>>
>> Regards.
>>
>> Iván Gómez Rodríguez
>> Ingeniero en Informática
>> mailto:igomez (AT) igalia (DOT) com
>> Telf: +34 986 10 76 10
>> Fax: +34 981 91 39 49
>> Igalia http://www.igalia.com
>>
>>
>
> That's a good hint. Thanks. Besides showing the error right up front on
> the page, were you also able to find it in any logs, say Apache error log
> file? My concern with showing error message on the page is it could
> reveal system config or file structure information. This time, since I
> already deleted temp_CACHED_* files and the back end came back up, I was
> not able to catch the error on the page. I'll try it next time.
>
> Bing

I checked Apache ssl_error_log and found

[client <my desktop IP>] PHP Warning: Cannot modify header information -
headers already sent by (output started at
/var/www/html/top/typo3conf/temp_CACHED_psad09_ext_tables.php:4470) in
/var/www/html/typo3_src-4.0.6/t3lib/class.t3lib_userauth.php on line 314,
referer: https://sitelogin.some.edu/cgi-bin/index.cgi
[client <my desktop IP>] PHP Warning: Cannot modify header information -
headers already sent by (output started at
/var/www/html/top/typo3conf/temp_CACHED_psad09_ext_tables.php:4470) in
/var/www/html/typo3_src-4.0.6/typo3/index.php on line 473, referer:
https://sitelogin.some.edu/cgi-bin/index.cgi

I wonder if that tells something? We use pubcookie for single sign on.

Bing
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Bing Du
> [client <my desktop IP>] PHP Warning: Cannot modify header information -
> headers already sent by

Generally quite harmless - might be caused for example extra space after
?>
On productive sites warnings are disabled.
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

"Bing Du" <bdu (AT) iastate (DOT) edu> writes:

>
> I checked Apache ssl_error_log and found
>
> [client <my desktop IP>] PHP Warning: Cannot modify header information -
> headers already sent by (output started at
> /var/www/html/top/typo3conf/temp_CACHED_psad09_ext_tables.php:4470) in
> /var/www/html/typo3_src-4.0.6/t3lib/class.t3lib_userauth.php on line 314,
> referer: https://sitelogin.some.edu/cgi-bin/index.cgi
> [client <my desktop IP>] PHP Warning: Cannot modify header information -
> headers already sent by (output started at
> /var/www/html/top/typo3conf/temp_CACHED_psad09_ext_tables.php:4470) in
> /var/www/html/typo3_src-4.0.6/typo3/index.php on line 473, referer:
> https://sitelogin.some.edu/cgi-bin/index.cgi
>
> I wonder if that tells something? We use pubcookie for single sign on.
>
> Bing

That looks like pubcookie produced an error, maybe becaue it could not
contact your login server.

Björn
--
Bjoern Pedersen
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english