Bug #17110
closed
Error showing pages after update to 4.1
0%
Description
After Updating to 4.1 AND doing the database-updates (seems not to happen without db-updates!) opening arbitrary pages returns:
-----------------------------------------------------------------------------------------
Warning: reset() [function.reset]: Passed variable is not an array or object in /usr/share/webapps/typo3/4.1/typo3/sysext/cms/tslib/class.tslib_content.php on line 2995
Warning: Variable passed to each() is not an array or object in /usr/share/webapps/typo3/4.1/typo3/sysext/cms/tslib/class.tslib_content.php on line 2998
Warning: Cannot modify header information - headers already sent by (output started at /usr/share/webapps/typo3/4.1/typo3/sysext/cms/tslib/class.tslib_content.php:2995) in /usr/share/webapps/typo3/4.1/typo3/sysext/cms/tslib/class.tslib_fe.php on line 2898
-----------------------------------------------------------------------------------------
Interestingly after deleting all cache the first page called shows up correct, but the second and all further are not displayed (only above error appears).
Locally installed extensions:
addressgroups
arotea_loginbox
chc_forum
ch_handbuch
csh_de
da_newsletter_subscription
de_phpot
dir_listing
dkd_imagemap
external_pageset
galileo_atom_export
goof_fotoboek
https_enforcer
iframeflexform
iim_feuserspasstype
ipmaskmountgroups
julle_events
julle_feedit
kickstarter
lastupdate
lz_table
macina_searchbox
make_printlink
mbl_newsevent
mf_pagetitle
mit_download
naw_securedl
newloginbox
n_extkeywords
nf_downloads
nuxos_randompassword
pil_mailform
quickpoll
realurl
sp_directory
sr_feuser_register
sr_static_info
static_info_tables
sys_stat
sys_todos
sys_workflows
tt_address
tt_news
(issue imported from #M5190)
Updated by Matthias Nagl about 17 years ago
It seems to have something to do with template caching because it works when I make the following changes in typo3/sysext/cms/tslib/class.tslib_content.php:
- comment out if-condition in line 2948
- commenting out else-block from line 2981 to line 2987
I think I disabled the problematic caching this way. I am going to use this as a temporary workaround but it shurely is not a solution...
Updated by Thomas Murphy about 17 years ago
I suddenly also had this error message after converting a page to the YAML (yaml.de) framework. I'm using the "rlmp_tmplselector" with it.
I think I was able to reproduce this problem that way and searched for the difference between both templates. YAML is done in iso-8859-1 encoding.
I edited it with an utf-8 editor, some characters were broken.
Seems they crashed the caching somehow, once I removed those characters, the template worked fine.
Maybe you could try if that works for you as well.
Updated by Michael Stucki about 17 years ago
This is a duplicate of #5088. Please try the proposed solution from there, and report if this works.