TYPO3 Core

Hmm, your problem-description is not really helpful:
PHP has hundreds of warnings available; should we guess what warning it is?

When does this error appear?
What did you do to get it?

Maybe you can also add a screenshot...

Hi!

I uploaded a screenshot. Here the following warning appears: Warning: Invalid argument supplied for foreach() in /var/www/vhostsdomain/httpdocs/typo3_src-4.2.0/typo3/template.php on line 1887
The warning comes always, when I log in to the BE:
In this example the warning is appear in the middle column, but in some cases it appears in the top of the recht column. (Now I don't have screenshot for this situation). But you are right. hundreed of php warning can comes in the BE...the problem is here with the skin. In the typo3. 4.2.0. the standard place where every warnings appear, causes, that I can't click on the save button, because the warnings overlaps them.

I reported this issue on the typo3-english list yet.

http://lists.netfielders.de/pipermail/typo3-english/2008-May/049442.html
http://lists.netfielders.de/pipermail/typo3-english/2008-May/049544.html
http://lists.netfielders.de/pipermail/typo3-english/2008-May/050047.html

Did you post that?
http://webempoweredchurch.com/support/community/forum/single_thread/getting-started/using-typo3-1/problem-afte-upgrading-to-typo-42/
If not: It is exactly your problem.

Does the guess by Jeff Segars help?
=> "Do you have any extensions installed that modify the pagetree or change the skin of TYPO3? Those seem like the most likely culprits for this kind of issue."

Maybe you can make a copy of the system and than try until you found the culprit...

I removed some extension, and the error doesn't come anymore. I don't know which extension caused.

OK, so your problem is (more or less) solved.
Now you have got to check which extesnion it was and replace it by something fullfilling your needs.

Maybe you can post that here then....

Hi!

I get this error again. I installed a complette new typo3 4.2.0, in installed the oelib, realty, realty_search, lib, div, rgsmoothgallery package succesfully. Atfer this I installed the dam, that ask to install the static_info_tables. At this point I get these warning.

Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /var/www/vhosts/domain/httpdocs/typo3_src-4.2.1/t3lib/class.t3lib_db.php on line 1009

Warning: Cannot modify header information - headers already sent by (output started at /var/www/vhosts/domain/httpdocs/typo3_src-4.2.1/t3lib/class.t3lib_db.php:1009) in /var/www/vhosts/domain/httpdocs/fejlesztes/typo3_src-4.2.1/typo3/template.php on line 632

Such warning can be resolve with update reference index and with compere the databas. The problem is here as I wrote above: the place of the warning. The text interfere with the bar above coming with the new typo3 (4.2.0) skin. Sometimes this bar holds important funciton (f.e. save button), and if you don't manage to resolve these warning, it can take that you can't save your modificaton.

My recommendation to think again this new skin, or any funciton to catch such php warning and show on other place.

I agree that the place where these warnings are shown is very prominent.

But if they were put somewhere else, people would just ignore them (for example you sound like you would do so then and I could understand that).
But then finally (always very surprisingly) the system does not work correctly anymore and the user is angry, complains about the quality of the product and so on...

Then in my opinion it is better to keep the messages where they are and to solve(!) them!

Also see #19048

I experienced a similar bug. In some cases the content overlaps the php warning. f.e. in list view I edit an item, and lot's of warning comes. This is problematic, f.e. If I'd like to debug this error. f.e. I add the krumo(variable) line to the source code, where the php warning comes from. In this case I can't see the result of the krumo, I can't debug the error.
I don't know what could be the right solution. I can imagine that make a "safe" typo3 be skin, where there isn't css layers.

I would like to confirm this issue. I just had a phone call by an BE user who could not save a content element because the save button was overlaped by the error message. (The BE user had deleted an image via filelist that was linked with the content element. So a warning was launched when opening the content element.) I think its not a bug and it is not relevant what exactly causes the error message or warning. But it is a severe usability problem.

This issue will be set to resolved as a duplicate of #18220.

#18220 already has a pending patch in the core list but its not accepted yet. Please test the solution of #18220 and vote in the core list or submit a better solution.