TYPO3 Core

Apologies! I just checked again, insert table is working brilliantly!

So the two functions that are not working are insert link and insert image.

I'm not worried about the insert image function because the built-in typo3 text+image function is great. But inserting hyperlinks is essential for the folk here who will be adding content to the site. I don't want them to have to add (potentially broken) code.

Further notes:

I have turned on troubleshooting and the output shows no trouble.

The one problem I have found is under the Information section for the extension in Ext Manager:

Code warnings:
(developer-relevant) It seems like there is a backend module in "mod1/conf.php" which is not configured in ext_emconf.php
The XCLASS filename-key "ext/rtehtmlarea/class.tx_rtehtmlarea_base.php" was different from "ext/rtehtmlarea/backup of class.tx_rtehtmlarea_base.php" which it should have been!

... I don't understand this. I have not changed the extension in the slightest! I have uninstalled and reinstalled it, that is all.

Please help!

Where did you get this copy of extension rtehtmlarea?

You should use your complete name when posting to this bug tracker.

Updated my profile.

It's the htmlarea rte extension that was included with typo3 4.1.2.

Delete the extension and get a fresh copy. Your site is corrupted.

There is no rtehtmlarea/mod1 directory in the rtehtmlarea extension distributed with TYPO3 4.1.2, nor is there a file rtehtmlarea/backup of class.tx_rtehtmlarea_base.php

I still do not see your full name.

thanks will do on Monday.

Strange, I added my full name to my typo3 login (the only place it appears I can edit my profile) and it hasn't synced with my bugtracker profile. I'll have another look.

Hi, I uninstalled the rtehtmlarea extension, deleted the folder and all its contents, and inserted the rtehemlarea folder from typo3_src-4.1.2.tar.gz I downloaded directly from typo3.org/download/packages/.

No change. All works exept insert link and insert image, which just reload the current page and wipe all unsaved changes when clicked.

I notice 4.1.3 is out. Should I update?

There is a difference now in what the ext manager information is showing for htmlarea RTE. The only problem it is now showing us under "Files Changed?":

<b>A difference between the originally installed version and the current was detected!</b>

Modified files:
class.tx_rtehtmlarea_base.php
htmlarea/htmlarea-compressed.js
htmlarea/htmlarea-gecko.js
htmlarea/htmlarea-ie.js
htmlarea/htmlarea.js
htmlarea/plugins/TYPO3HtmlParser/typo3html-parser-compressed.js
htmlarea/plugins/TYPO3HtmlParser/typo3html-parser.js
htmlarea/plugins/TYPO3Browsers/typo3browsers-compressed.js
htmlarea/plugins/TYPO3Browsers/typo3browsers.js
htmlarea/plugins/Acronym/acronym-compressed.js
htmlarea/plugins/Acronym/acronym.js
htmlarea/plugins/UserElements/user-elements-compressed.js
htmlarea/plugins/UserElements/user-elements.js
mod5/class.tx_rtehtmlarea_user.php

This is a bit odd because this source is what I used in the first place!

EDIT: on a side note, my full name is James Knuckey. I have submitted bug report #0006656 regarding my typo3.org profile not syncing with my bugtracker profile.

Is the rtehtmlarea directory inside typo3/sysext directory?

What Default Configuration Settings are you using?

By the way I observe the described behaviour with the trunk version (1.6.2dev). Any popup causes it actually, including the About window. The popup appears, closes itself right away and the page reloads.

I cannot reproduce this behavior neither with 1.5.3, nor with 1.6.2dev.

Try to delete all files in typo3temp with names starting with 'rtehtmlarea_' and to clear the browser cache.

Unfortunately, the problem persists. Here's what I did:

- removed all the files called rtehtmlarea* from typo3temp
- deleted the directory called typo3temp/rtehtmlarea
- cleared the browser cache

When all that is done, the popup window seems to come up normally, but closes automatically after about 5 seconds. After is has closed, the frame with the content element is reloaded.

Note that I don't have this behaviour with current production version (1.5.4), but only with trunk (1.6.2dev).

I thought the problem might have been related to the latest Firefox update (2.0.0.9), but I tried with an old-ish version of Camino (which is also Mozzilla-based) and observed the same behaviour. I can't test with IE right now...

Just to be complete, I'm using rtehtmlarea 1.6.2dev in conjunction with latest SVN version of TYPO3.

Please open a separate issue for 1.6.2dev. Obviously it is not the same problem as the one originally reported in this issue. Please report any javascript error showing up on the console.

Done: http://bugs.typo3.org/view.php?id=6676

Okay. I've had time to properly look at the problem. I removed and deleted the extension, deleted all references to it I could find. Then I added it back in from typo3 source and installed it again... And now it does work - except for in Opera.

Seems I have gotten it down to a browser-specific problem.

I un-ticked the "Enable the RTE in Opera 9" and the RTE did not load in Opera - but it worked fine in FF and IE. In these browsers, I'm finally seeing the popup dialog for inserting links and images.

I ticked the "enable in Opera" box again and the RTE now works ok in Opera - except for the insert-link and insert-image buttons, which are doing the same as before: no popup when I click, just reloads the edit page and wiping out unsaved changes.

FF and IE are continuing to work. So it's ok I can use another browser - it would be nice to be able to use Opera as I use it for everything else. Then again, the ones who will be using the RTE most will be the content editors, not me, and they're generally using either FF or IE anyway. For the time being I'll have to tell them to specifically not use Opera, which irks me a little bit.

Did you delete all files with names starting with 'rtehtmlarea_' in directory typo3temp?

Did you clear the cache of the Opera browser?

I cannot reproduce this problem using Opera 9.24. Could you report any javascript error displayed by Opera on its Error console?

Well what do you know! Clearing Opera's cache got rid of the problem finally! I shoulda thought of that shouldn't I. :)

I still don't know exactly how I got the problem in the first place. I shall be extra careful with extensions from now on. This problem has actually helped me understand the extension system a lot more.

Mr Rolland I very much appreciate your prompt replies even though it wasn't strictly a bug. I think. I can see you are very motivated to make this a good extension! Great support, thank you very much.