Last modified: 2011-07-27 23:25:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T25254, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23254 - fullurl link corrupted by Rich Editor
fullurl link corrupted by Rich Editor
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
FCKeditor (Other open bugs)
unspecified
All Windows XP
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-19 23:15 UTC by Johann A. Fannberg
Modified: 2011-07-27 23:25 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Johann A. Fannberg 2010-04-19 23:15:48 UTC
MediaWiki edition: 1.16 alpha
FCKeditor version: newest, as of today.

Problem description:

When editing a page containing a fullurl link, it gets corrupt:

Correct link: [{{fullurl:somepage|action=edit}} change]

When entering Rich-mode, the link obviously gets corrupt and looks something like this:

[{{fullurl:somepage|action=edit}} change]

Entering Rich- mode a second time, the url now becomes;

[{{fullurl:somepage|action=edit}} change]

The third time:

[{{fullurl:somepage|action=edit}} change]

End of test.

It looks like the fullurl syntax is unknown to the FCKeditor (converter at some level), and the escape sequence produced is also not handled in a "consistent" manner.


Kind regards, 

Johann A. Fannberg.
Comment 1 Chad H. 2011-07-27 23:25:51 UTC
Copied from bug 30075:
> Per this upstream bug http://dev.ckeditor.com/ticket/5602 
> 
> "FCKeditor and MediaWiki are no longer supported. Closing the ticked as invalid."

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links