User talk:Robchurch/Integrating FCKeditor with 1.9.3
Update[edit]
Regarding this update, I discovered, while chatting to some users on IRC, that I'd made a couple of incorrect assumptions when developing this patch.
$wgAllowRawHtml had no effect whatsoever on what HTML was being allowed, because of course, it requires that HTML is wrapped in <html></html> tags, and the behaviour here was not the same at all. I realised that the reason tags such as <script> were being filtered out was due to the MediaWiki sanitiser, which also caused problems with, e.g. tables, due to the insertion of some tags not on the Sanitizer whitelist.
I've since updated the instructions to remove the useless alteration to LocalSettings.php, and included some alterations to the Sanitizer class in the patch which will whitelist the a and img tags, as well as tbody; as far as I can see, these are the immediate obstacles to using almost all of the editor's functionality, and are going to be relatively harmless in a trusted editing environment. robchurch | talk 13:33, 13 June 2007 (UTC)
how to get wiki syntax and fckeditor to cooperate?[edit]
When I implemented your patch I found that wiki syntax was now ignored completely. My headings, lists, and emphasized text was all just strung together with a few line breaks here and there. How can I set it up such that wiki syntax and fckeditor can work together? (This was made by Gschnaub)
- FCKeditor doesn't understand wiki-syntax, it understands HTML. Pre-made articles with Wiki-syntax will be messed up, since they're not parsed before they're sent to the editor. It's possible to parse the wiki-code to HTML before it's sent to the parser by running the $wgParser->parse function to $text in the getContent function under includes/EditPage.php - however this leaves a couple of other problems:
- The parse function creates the table of contents, which you ofcourse do not want to be added extra each time you edit the page
- The "script" tag for the table of contents is added so you'll be able to hide/show the TOC.
- You get a lot of "anchor points" (<a name="subtitle"></a>)
- The HTML parser doesn't include the categories, so you'd loose all the categories for an article each time you edit it.
- There are probably some other I haven't encountered yet.
- Ofcourse, it's possible to fix this by running some regexp replacements on the content before it's sent to the editbox and you can run a regexp match to get the categories from the content before it's parsed to HTML and append it to the content sent to the editor. I'm currently doing this, but since it's basically untested and I'm not that into the MediaWiki sourcecode yet there are probably a number of problems I've yet to encounter. Zido 08:01, 6 July 2007 (UTC)
does this integrate the fck-editor as default?[edit]
.. or do i have an activation-tag like __USE_EDITOR__ ?
- FCKeditor becomes the default editor. robchurch | talk 17:06, 6 July 2007 (UTC)