Project

General

Profile

Actions

Bug #23962

closed

Content Wizard brocken

Added by Daniel Felix over 13 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-11-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hello,

i've encountered a crash/block at the content wizard.

Since i upgraded to 4.4.x this problem occures randomly, but it seems that it has been worser in version 4.4.4.

If i try to create a new content element on clean new page, or even on a page with content elements, i just get a blank grey screen. NO Plugins, CE's or other things which could be selected.

The behaviour is like the bug at templavoila: 13052
But I don't use templavoila, it isn't even installed/uploaded.

I could get the CE-Wizard working if i activate my Firebug and force my browser to reload every pagecontent.

I hope this helps. If you need further test, please let me know.

(issue imported from #M16275)


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #23950: Empty backend frame width FirefoxClosed2010-11-05

Actions
Actions #1

Updated by Susanne Moog over 13 years ago

Do you have compressionLevel set in the install tool?
Have you enabled all the debug / error reporting options in the install tool?
Does firebug show a JS error?
Does it happen in every browser?
Do you have any special extensions installed?

I'm sorry, I ask so many questions but I'm searching for a way to reproduce this.

Actions #2

Updated by Daniel Felix over 13 years ago

Well i tried it with my productive enviroment and with a fresh and clean instance.
so i think it can't be any ext.

[BE][compressionLevel] = 0

This error currently just occure in FF and FF-like Browser (which use the Gecko-Engine).

I haven't seen any error. Even if Firebug was active and JS-Debugging was activated. But it's hard to analyze it with firebug, cause if it is activated, my ce-wizard works correctly. Maybe there wrong cache-header?

Actions #3

Updated by Marcus Balasch over 13 years ago

I've got the problem on some websites and can show it via Teamviewer

Two ways to restore the content:
1. reload the actual Frame via contexmenu
2. disable the firefox-cache in the webdeveloper toolbar

This hints can help perhaps

Actions #4

Updated by Stefan Galinski over 12 years ago

  • Status changed from Needs Feedback to New
  • Target version deleted (0)
Actions #5

Updated by Alexander Opitz about 10 years ago

  • Status changed from New to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF