Bug #18220

typo3-docheader not visible when error occures

Added by Ingo Schmitt almost 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2008-02-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When an PHP Warning is issued in the backend, the typo3-docheader rendered below the errors, thus the buttons could not be clicked

I know, in production systems, you shouldn't rais Errors in the FE, but for Developing it's quite nice.

See attaached Image
(issue imported from #M7544)


Files

TYPO3 4.2.0beta1a_1203098861409.png (56.5 KB) TYPO3 4.2.0beta1a_1203098861409.png Administrator Admin, 2008-02-15 19:11
patch-7544.txt (528 Bytes) patch-7544.txt Administrator Admin, 2008-03-18 16:19
after_patch_1205853793567.png (51.4 KB) after_patch_1205853793567.png Administrator Admin, 2008-03-18 16:21

Related issues

Related to TYPO3 Core - Bug #18734: SQL debug output is not shown in the BackendClosedSteffen Kamper2008-05-01

Actions
Related to TYPO3 Core - Bug #21570: Debug output destroys BE HTMLClosedSteffen Kamper2009-11-16

Actions
Related to TYPO3 Core - Bug #21557: Use flash messages to show SQL debug errors in the backendClosedSteffen Kamper2009-11-15

Actions
Has duplicate TYPO3 Core - Bug #19048: Backend content saving button are overwritten by php-warningsClosedChristian Kuhn2008-07-02

Actions
Has duplicate TYPO3 Core - Bug #18980: warnings interferee with the save buttons.ClosedChristian Kuhn2008-06-18

Actions
Has duplicate TYPO3 Core - Bug #20056: Error messages block TYPO3 4.2ClosedChristian Kuhn2009-02-19

Actions
Has duplicate TYPO3 Core - Bug #20034: Trouble with dbal deactivation in 4.2 updateClosedChristian Kuhn2009-02-17

Actions
Has duplicate TYPO3 Core - Bug #18995: CSS Display Error in Firefox 3.0ClosedChristian Kuhn2008-06-20

Actions
#1

Updated by Benni Mack almost 13 years ago

We should have something for all errors and outputs etc. there, not just the ones done by PHP.

#2

Updated by Ingo Renner almost 13 years ago

I've seen this now, too

#3

Updated by Ingo Renner over 12 years ago

removed from 4.2 as it's no blocker and will happen most likely during development only anyways

#4

Updated by Ingo Schmitt over 12 years ago

I think it's a blocker, as you can't work with the backend (no Icons). Is it to late to provide a patch?

#5

Updated by Steffen Kamper over 12 years ago

using cc_debug works.

#6

Updated by Ingo Schmitt over 12 years ago

Attached patch corrects CSS for TYPO3 Backend, so that edit icons are always on top. Screenshot also attached. Patch will be posted to core list in a few minutes

#7

Updated by Steffen Kamper over 12 years ago

Hi Ingo,

i don't think this is a good solution. Output looks crap also.

We need a proper solution for this, maybe integrating cc_debug.

#8

Updated by Ingo Schmitt over 12 years ago

Output looks crap, but it's working. As Ingo mentioned, it will happen most likely during development only anyways. So this is a better solution than none solution !

#9

Updated by Christian Kuhn almost 12 years ago

This is still a usability problem for setups with enabled php warnings in productive environments, see #18980 for some more user feedback.

Any chance to find an acceptable solution?

#10

Updated by Christian Hernmarck almost 12 years ago

I think it's no problem to disable displaying php errors (or at least lowering the error-level - only errors but no warnings) and enabling a php-error-log (file).

This may be suggested in the TYPO3-setup so the non admins know that there is something...

#11

Updated by Benni Mack over 10 years ago

solved with #18734

#12

Updated by Susanne Moog over 9 years ago

  • Target version deleted (4.4.0)

Also available in: Atom PDF