TYPO3 Core

wwell.. the problems happens also with beta2.. but just with some sites of mine..

the fact is that they use the SAME typo3_src !!

i guess there is some extension that cause problems....

I am using beta3 (also used beta2) with Safari and it works fine for me. Safari v. 2.0.3, 417.8

the problem is that this behaviour is quite random.
i could make it work for a few minutes (deistalling an extension via firefox)..
Safari was loading everything perfectly.. then it began to not load the alt_menu anymore.

and i have several websites using the same 4.0beta2/3 source .. some works, other don't

very strange, isn't it?

Safari: 2.0.3 (417.9.2)

I tested it now for a while with several settings, and the problem didn't apear on my system.

You have to describe it better. Which extensions did you install / uninstall, do you use the news skin or not (it tested it with both), what do you exactly 'click' bevore it happen, and how does it look like (upload screenshot).

yes i'm doing heavy testing.. since the problem still exists with 4.0rc2..

right now i have 5 websites, using the same typo3_src and files structure..
2 of them give me this problem.

interesting: loading the alt_menu.php in a new window works perfectly.

so it is the main frame page that seems to have problems in asking the browser to load that address.

You have to describe the bug better.

I tried rc1, beta3, with and without new skin, usage of the menus and so on, it works...

ok, found something interesting:

the problem happens only if i have "Start up in the module 'Task Center':" checked

(with just the simple taskcenter ext loaded)

i tried with 3 different Safari and it always happens

i uploaded a screenshot.

it is just an empty, not loaded frame.

if you can't reproduce it, i can give you a test account

Ok that with the taskcenter was the important information!

Bugreport:

1. Startup in Task Center has to be enabled
2. The Menu isn't loaded after login, if you reload, everything seams ok...

There is some kind of javascript foreward to the taskcenter I think, perhaps that's the problem... I won't fix it :-)

Sounds like an issue for Julle...

I'll take a look it. I have no mac though..., but Konqueror doesn't load the taskcenter on startup, even if it's checked.

Since both browser are khtml based that problem might be co-related.

Safari 2.0.4 (419.3), Typo3 4.0

No vertical menu and no tasks when start up in tascenter is activated . Even if page gets reloaded. Got safari enhancer, activated JS console but no JS error shows up.

- Fails 100% if "Start in Taskcenter" is set via User or Group-TSconfig like this:

setup {
startInTaskCenter = 1
override {
startInTaskCenter = 1
}
}

- The user can use this feature more or less if he checks the checkbox "Start up in the module 'Task Center'" in his Setup. But sometimes suddenly the left navigation bar does not appear when the whole Backend gets reloaded.

Tested with Safari Version 2.0.4 (419.3) and TYPO3 4.0.2.

Christian, can you try to fix this on your own? I have no Mac here, so I won't be able to look at it...

any news about this bug?
maybe new Thomas's "startup module" feature does fix it? anybody has already tried it?

I will look at this this evening when I have a mac under my fingers. ;-)

Greets,
Thomas

I can't reproduce this on my Mac (Safari Version 2.0.4 (419.3)). Wether in version 4.1 nor SVN Version.

Does this error still occur somewhere?

Greets,
Thomas

Similar problem here. Clearing the FEcache results in empty frame as well as adding any content to a page. Happens with Firefox 2.0.0.7 and Internet Explorer 6.0.

Everything worked fine until I had to install a backup version. So it could be an server configuration or version problem.

System:
Debian 3.1
Apache 2 (20051115 )
MYSQL 5.0.45
PHP Version 5.2.3
Typo 4.1.2

[edit]
Found the solution: Extension "static_info_table" causes this behavior. Update to 2.0.5 solves this problem. (thanks to www.typo3.net)
[/edit]

FYI / Good news: I can not reproduce this issue in TYPO3 Version 4.2.0ALPHA1 anymore when I use the new "Start up in the following module"-Feature.

I could access all the modules without problems. :->

And: "setup.startInTaskCenter" does NOT work anymore, which is IMO perfectly OK...

i agree: this bug is resolved with Typoe 4.2 new startup modle selector...

(maybe this feature could be ported later to 4.1 branch

Resolved with changes integrated in TYPO3 4.2 and newer; no further change required.