TYPO3 Core

This is NOT about an extension but about the usual backend form when editing editing the TypoScript within the Template section.

So could someone please change the Project back to TYPO3 Core?

I can confirm this on IE7 with the old way (no t3editor at all) of editing template setup.

may be related to Jeff's fix in #18392

Same behaviour in 4.2.0 RC1

can you reproduce this behaviour in the final 4.2 version?
i can't so i guess this bug can be closed.

this is not t3editor releated, right?

can someone please move this issue to TYPO3-core?

... and connect it to 8049 as well

not t3editor related.
please move to "core"

i can't reproduce this issue.

is this solved by 7781?

7781 should only affect saving from the Constants Editor and not from Info/Modify. I'll try to duplicate this soon and see what I can tell.

I can reproduce this behaviour with IE7 (Win XP), when I edit "Constants", "Setup", "Description", etc. separately.
When I save the document, the site comes back again with not having saved my changes.
Also clicking the "close"-button brings the same page back again.

If I edit the whole template record, it works like designed :-)
I also can confirm that Firefox does what he is told.

I tested this on a new installation with the same results.

Thanks Manuel. Does the actual Constants Editor work for you? (vs. the Constants section with a textarea)

I'd guess we need the same fix as 7781.

Hi Jeff,

yes, the Constant Editor works for me.

Just attached a patch that should clear this up. Once I get a little confirmation here, I'll go ahead and propose it on the core list.

Hi Jeff,

with this patch I can save the document, so it works :-)

Now we need another one for the "Close document"-button.
This one only reloads the page and doesn't redirect back.

Sorry for the delay in getting back to this patch. Attaching a new version here that fixes the close button also. I'll put this on the core list later today.

Jeff,

thanks a lot for the patch!

Manuel,
If this is working for you, could you reply on the core mailing list. I still need a +1 from someone who has tested it before it can go into 4.2.1.

Thanks!

Committed to 4.2 branch.