TP-Docs
HTML5 Icon HTML5 Icon HTML5 Icon
TP on Social Media

Recent

Welcome to TinyPortal. Please login or sign up.

Members
  • Total Members: 3,963
  • Latest: BiZaJe
Stats
  • Total Posts: 195,917
  • Total Topics: 21,308
  • Online today: 445
  • Online ever: 8,223 (February 19, 2025, 04:35:35 AM)
Users Online
  • Users: 0
  • Guests: 415
  • Total: 415

[bugtracker] FCKeditor cannot insert link!

Started by misjka, October 20, 2008, 04:04:10 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

misjka

This is an old bug from tp098:

After upgrading to Firefox 3 the editor cannot insert weblinks properly.

1) When inserted a link, the next thing that will happen is that the insertion window reappears showing the link settings just inserted. The window re-popups when the user is pressing the Save button or the vertical browser slider.

2) When have saved the article/HTML-block the link is corrupt, though. Checking it up, one only gets a string like e.g. "javascript:void(0);/*1224514253121*/" where the link should go.

3) Reentering the correct link a second time it is saved properly, though. This means that every link has to be created twice, and so must the article be saved twice, before it works correctly.


ed_m2

ah yes.. i had this too...

first time returned javascript call, second time worked fine.

thought it was just me.

IchBin

Most likely a bug in the editor and not TP.

feline

A update to lastest version of FCKeditor helps .. v 2.6.3

Fel

misjka

Quote from: feline on October 21, 2008, 07:35:02 PM
A update to lastest version of FCKeditor helps .. v 2.6.3

Fel

Ah, thanks Fel :)! Then I presume that v263 will be included in the TP beta 3 then ;) ?! Because whether or not it's a TP bug technically speaking, it must still be considered a bug in the TP concept, after all...?!

IchBin

Personally I think we should drop all the editors. They have caused nothing but trouble.

misjka

Upgraded to the latest FCKeditor myself and it worked like a charm *this far, cough-cough *... ;D

G6Cad

#7
Just as a sidenote here now.
If you run into errors or issues now with that editor, we will not be able to give you support on it as it's not what Bloc have coded in to TP  :-\

misjka

Yup, thanks for your note, G6 :). I will only use it on my test site to see what comes out of it...

sturmkatze

#9
Quote from: IchBinâ,,¢ on October 22, 2008, 03:33:24 PM
Personally I think we should drop all the editors. They have caused nothing but trouble.
I disagree about removing the editors. Most people don't want to code... yeah, people should know how, but it's a pain, especially tables, etc. It seems to work okay, except for this thing. Why should I not update the editor? Will an update be in the next beta?

This website is proudly hosted on Crocweb Cloud Website Hosting.