[TYPO3-core] RCF: #8157 t3editor don't work in Fx, IE7 and Opera(saving)

Erik Svendsen erik at linnearad.no
Sat Apr 19 14:13:57 CEST 2008


Hello Dmitry Dulepov [typo3],

> Hi!
> 
> Erik Svendsen wrote:
> 
>> To me it looks like there are multiple issues in t3editor. Neither of
>> them are any blockers to the release of 4.2 in my opinion, but
>> t3editor should be moved out of core if not solved.
>> 
> I disagree. If we follow your proposal, we should move lots of things
> outside of core (anything with bugs). May be we should drop the whole
> core because it has bugs. Bugs are not the reason to exclude something
> from core.

If bugs are serious enough or probably will affect a large percent of users 
(make the extension not usable for them) it should be moved from core to 
a normal extension until the bug is solved. Small bugs who are not really 
any problem, no problem at all. 

> Btw, if you found bugs, you should report them to BT. Putting them
> here is not the right step on the way to solve them.
> 

Has!!!  http://bugs.typo3.org/view.php?id=8157. Before I wrote my first post.

But when I get the same problem on 5 different installations on 3 different 
servers in 3 different browser on 3 different OS on 4 different PC i think 
there are a problem. Of course there could be other explanations than bugs

I have also tested 3 of the installations with RC1, no real problem at all 
with t3editor, I got the problem wirh RC2. Tried also reinstall t3editor, 
did not help.

> Or you can stop using t3editor. But you should not prevent others to
> use it.
> 

I don't prevent others from using it. But if this is a bug who affects enough 
user, it will hurt the reputation of TYPO3. It could still be accesible as 
a normal extension.

>> First: With t3editor installed and activated in template module it's
>> impossible to save changes.
>> 
> Not exactly. I had similar issue yesterday but could not reproduce it
> later.
> 
> When I tried to save, changes were not saved. There were no JS errors
> but after save I saw old TS.
> 
> What I did is: I took TS into a regular text editor (TextEdit on Mac)
> and reformatted it manually to see if there are any errors. Could not
> find any but as a result I made a good cleanup of a long TS from my
> test site.
> 
> Pasted it back to t3editor and could save without problem. Why? No
> idea.
>

Have tried writing clean TS code in new template . Tried coping in code (clean), 
all with no sucsess. Of course I can save with t3editor deactivated.
 
>> Second: Deactivating t3editor in template modul makes it impossible
>> to activate it again.
>> 
> Not true. See: http://www.screencast.com/t/T9zf4OI2
> 
> Again, if you found a bug, it can be solved only if you report it.

Even after uninstall and reinstall I can't reactivate it. And I have tried 
t3editor since beta2, and this bevavior is only in RC2. In Fx it looks like 
it activated (same in Opera), but as soon as I save it is deactivated again. 

>> It also looks like there are some minor inconsistent behavior in the
>> editor, regarding autocomplete, tabs and newline.
>> 
> Possible. This is a new code. True for most of new code. There are
> many glitches even in the code introduced in 4.0!
> 
>> To me this part of TYPO3 4.2.0 is still real Alpha and should be
>> dropped in the 4.2 release. I can't give any patch, only the advice
>> to drop t3editor from 4.2, release it as a normal extension when it's
>> ready and put it in the core for a later version.
>> 
> I completely disagree. I use t3editor often and it is wonderful thing.
> I really love it!
> 

I also love it when it works, which it has until i upgraded my RC1 and Beta3 
installations to RC2 yesterday. So it's nothing more I want that it's working 
and being a part of 4.2

And it's also reported earlier that it doesn't work i IE7, http://bugs.typo3.org/view.php?id=7509.

And I have tried to get Firebug to give me any clues, but haven't managed 
it to throw any errors.

Fx = Firefox

WBR,
Erik Svendsen
www.linnearad.no




More information about the TYPO3-team-core mailing list