• Inhaltsverzeichnis dieser Seite
• FCKeditor / FCK Editor / CKeditor
• News von der Source-Forge-Projektseite zu neuen Versionen
• Inhaltsverzeichnis des Handbuchs mit Deep-Links zu den einzelnen Kapiteln
• FCKeditor Anwender-Handbuch (User-Guide)
• amazon
• Aus dem User-Archiv: Onlinelitertaur zum Thema FCKeditor
• Einbindung und Konfiguration des FCKeditors gemäß Handbuch
• FCKEditor unter Firefox
• FCKEditor mit Plugins erweitern
• FCK-Editor unter Safari / Mac
• Amazon: Bücher
• Saulmades FCK-Editor Seite
• HOWTO -Get absolute urls with the filemanager (absolute Pfadangabe für Upload-Pfade)

Features im Überblick:

• Schrift- und Text-Formatierung
• Textfunktionen wie Copy&Paste, Undo, Redo
• Erstellen von Links
• Setzen von Ankern
• Einfügen von Bildern
• Erstellen und Bearbeiten von Tabellen und Formularen
• Anpassung der Toolbar
• Unterstützung von Skins
• Rechtschreibprüfung
• Unterstützung von CSS
• automatische Anpassung an Browser

Homepage: http://www.fckeditor.net

Projektseite: http://sourceforge.net/projects/fckeditor/

Projektseite/Bugs: http://sourceforge.net/tracker/?group_id=75348&atid=543653

Projektseite/Patches: http://sourceforge.net/tracker/?group_id=75348&atid=543655

Projektseite/Forum: http://sourceforge.net/forum/?group_id=75348

Projektseite/News: http://sourceforge.net/news/?group_id=75348

Link zum Handbuch: http://wiki.fckeditor.net

FCKeditor.Java 2.6 released!

A new release of our Java dedicated integration for FCKeditor is available.

This version contains a few minor fixes including:

* Removed deprecated code and skim methods.
* Added separate input name attribute in JSP tag.

This is supposed to be the last release for the 2.x series. Thanks to Michael Osipov for his continuous support to the FCKeditor.Java project.

Check out the FCKeditor.Java website for more information:

FCKeditor 2.6.5 released

A new major release of our good and widely known FCKeditor is available. We've been focused on fixing small compatibility issues with some browsers (IE8 mainly) and porting a nice feature introduced with CKEditor 3, our unique Spell Check As You Type (SCAYT) solution.

This release also introduces some important security fixes. Upgrading is highly recommended.

Read more at our blog:

FCKeditor.Java 2.4.2 released

This is a bugfix and security release. This means that this is a drop-in release. Drop and deploy. No changes.

FCKeditor.Java 2.5 Beta 1 released

The so waited release of our native Java integration is here. This is another important step to bring a richer and more stable experience for Java developers.

The following are the most important new features:

* Connector interface, arbitrary connectors are now possible.
* More user action control.
* Default implementations chosen by default.
* Localizable messages backed by a LocaleResolver interface.
* Internal improvements.

FCKeditor 2.6.4.1 released

This is an important security release. Upgrading is strongly recommended.

FCKeditor 2.6.4 released!

The stabilization of FCKeditor 2.6.4 Beta has been completed successfully. We are proud to come with a brand new version of our editor, ready for production use.

As of this version, we're offering the WebSpellChecker integration, a zero-installation solution for spell checking provided by SpellChecker.net. You will now have a wonderful spell checker running out of the box, requiring no server side installations and configurations.

Several bug fixes and new features have ...

FCKeditor 2.6.4 Beta released!

This new version introduces the WebSpellChecker integration, a zero-installation solution for spell checking provided by SpellChecker.net. You will now have a wonderful spell checker running out of the box, requiring no server side installations and configurations.

Several bug fixes and new features have been added, especially to our table support, including the ability of defining header rows and columns to tables. Special thanks to Alfonso Martinez and Koen Willems for their ...

FCKeditor.Java 2.4.1 released

This is a minor release, fixing some small issues found with version 2.4. For more details, please visit our dedicated web site for the Java Integration (http://java.fckeditor.net/).

FCKeditor: 2.6.3 released

Online text editor (DHTML editor), for ASP, ASP.NET, ColdFusion, PHP, Java and JavaScript brings to the web many of the powerful features of known desktop editors like Word. It's XHTML compliant and works with Firefox, Mozilla, Netscape and IE.


The stabilization of FCKeditor 2.6.3 Beta has been completed successfully with a few minor issues being fixed. We are happy to bring another nice release to public, with some important new features.

FCKeditor 2.6.3 Beta released

This new release brings some nice new features to FCKeditor like the DIV Container Tool, "non breaking space" support and automatic e-mail protection. As usual, it also includes some minor fixes.

We'll be waiting a few days to catch some feedback for this beta. The stable release is planned to 5 August 2008.

Now, we're fully focused on the CKEditor 3.0 development, our next generation editor. It will be the great new thing in online text editing.

Stay ...

• General Info

  • License

  • Support

  • Performance

  • Donations

• Developer's Guide

  • Installation

  • Integration

    • Javascript

    • ASP

    • ASP.Net

    • ColdFusion

    • Java

    • PHP

    • Other

  • Configuration

    • Configurations File

    • Toolbar

    • Styles

    • Templates

    • Spell Checker

    • Built in File Browser

  • Customization

    • Plug-ins

    • Scripts Compression

    • Skins

    • Custom File Browser

    • Debugging

  • FCKeditor Javascript API

  • Names and Concepts

    • Commands

  • Code Overview

  • Participating

    • Server Side Integration

    • Localization - interface translation

    • Documentation

• FAQ - Frequently Asked Questions

• Introduction to the User's Guide

• FCKeditor Overview

• Quick Reference

• Interface

  • Toolbar
  • Editing Area
  • Context Menu

• Common Tasks

  • Writing
  • Text Formatting
  • Creating Lists
  • Links, E-Mails and Anchors
  • Inserting Images
  • Tables
  • Cut, Copy and Paste
  • Templates

• Other Tasks

  • Find and Replace
  • Undo and Redo
  • Spell Checking
  • Printing

• Source Editor

• Keyboard Keystrokes

• Compatibility

 

Zunächst Installieren:

Zip-Datei herunterladen
z.B.:http://www.fckeditor.net/download/default.html

In einen Ordner "FCKeditor" in der Ausgangsebene (root) der Website entpacken.
Bei Wahl eines anderen Ordners, muss eine BasePath-Anweisung eingefügt werden (siehe unten)

---

Einbindung als Javascript in normale HTML-Seiten (nicht PHP!)

2 Methoden

1. Die inline Methode (bevorzugt):

Head:

<script type="text/javascript" src="/FCKeditor/fckeditor.js"></script>

Body:

<form ...>
<script type="text/javascript">
  var oFCKeditor = new FCKeditor( 'FCKeditor1' ) ;
  oFCKeditor.BasePath = "/FCKeditor/"
  oFCKeditor.Create() ;
</script>
<submit ...>
</form>

2. Die textarea-Methode

Head:

    <script type="text/javascript" src="/FCKeditor/fckeditor.js"></script>
    <script type="text/javascript">
      window.onload = function()
      {
        var oFCKeditor = new FCKeditor( 'MyTextarea' ) ;
        oFCKeditor.BasePath = "/FCKeditor/" ;
        oFCKeditor.ReplaceTextarea() ;
      }
    </script>

Body:

 <form ...>
 <textarea id="MyTextarea" name="MyTextarea">This is <b>the</b> initial value.</textarea>
<submit ..>
</form>

Entscheidend ist das "name"-Attribut; es ist nützlich, um Verwirrung zu vermeiden, diesselbe ID-Bezeichnung zu wählen

---

Einstellungen

Breite (voreingestellt: "100%")

Möglichkeiten:

    oFCKeditor.Width = 400 ; // 400 pixels
    oFCKeditor.Width = "250" ; // 250 pixels
    oFCKeditor.Width = "80%" ; // 80 percent

Höhe (voreingestellt: 200)

Möglichkeiten:

    oFCKeditor.Height = 400 ; // 400 pixel
    oFCKeditor.Height = "250" ; // 250 pixels
    oFCKeditor.Height = "100%" ; // 100 percent

Voreingestellter Textinhalt:
voreingestellt: <empty>

oFCKeditor.Value = "<h1>Testing</h1>This is a <b>sample</b>." ;

BasePath
Pfad festlegen, wo die FCKEditor Dateien sind
voreingestellt: oFCKeditor.BasePath = "/FCKeditor/" ;
Relative Pfade vermeiden. Von Root starten (/). Immer mit Slash enden (/)

    oFCKeditor.BasePath = "/Components/FCKeditor/" ;

Fehlermeldungen unterdrücken:

    oFCKeditor.DisplayErrors = false ;

---

Einbindung des FCKeditors in PHP-Seiten

Quelle: http://wiki.fckeditor.net/Developer%27s_Guide/Integration/PHP

Zunächst include (z.B. am Beginn der Seite):
:

include("FCKeditor/fckeditor.php") ;

Anmerkung: Alternative, gefunden auf http://www.thomann-wyss.ch/blog/  mit dem Vorteil, dass mit __FILE__ das Problem der relativen Pfaden bei Include-Dateien gelöst ist

include(dirname(__FILE__)."/FCKeditor/fckeditor.php");

An gewünschter Stelle im Body-Bereich, innerhalb des <Form>-Blocks:

[? php
$oFCKeditor = new FCKeditor('FCKeditor1') ;
$oFCKeditor->BasePath = '/FCKeditor/';
$oFCKeditor->Value = 'Default text in editor';
$oFCKeditor->Create() ;
?]

Die Instanz, die hier gebildet wird, verhält sich wie ein <INPUT> field in einem Formular. Es wird denselben Namen annehmen, den Du ihm mit obigem Befehl gibst, hier also "FCKeditor1". Es entsteht also eine Übergabe-Variable mit dem Namen FCKeditor1, einlesbar z.B. mit $_POST['FCKeditor1'] oder stripslashes( $_POST['FCKeditor1'] ) ;

Komplettes Beispiel:

[ ? php
include("FCKeditor/fckeditor.php") ;
?]>
<html>
  <head>
    <title>FCKeditor - Sample</title>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <form action="savedata.php" method="post">
[ ? php
$oFCKeditor = new FCKeditor('FCKeditor1') ;
$oFCKeditor->BasePath = '/FCKeditor/';
$oFCKeditor->Value = 'Default text in editor';
$oFCKeditor->Create() ;
?]
      <br>
      <input type="submit" value="Submit">
    </form>
  </body>
</html>


Ausgabe in Variable umleiten (statt Direktausgabe)

$output = $oFCKeditor->CreateHtml() ;

---

Einstellungen bei PHP-Einbindung:

Höhe, Breite:
vor dem Create() -Befehl  oder dem CreateHtml() - Befehl

$oFCKeditor->Width  = '100%' ;
$oFCKeditor->Height = '200' ;

---

UPLOAD-PFAD

To set the path for saving uploaded files uncomment the following line in /FCKeditor/editor/filemanager/browser/default/connectors/php/config.php.

// $Config['UserFilesPath'] = '/UserFiles/' ;
Um den Pfad für UPLOAD-Dateien zu setzen, folgende Zeile  entkommentieren   in:  /FCKeditor/editor/filemanager/browser/default/connectors/php/config.php.

// $Config['UserFilesPath'] = '/UserFiles/' ;

Übersetzer-Anmerkung: die Zeile ist  je nach Version evtl. schon von vornherein entkommentiert, also ohne Slashes am Anfang;
so dass nur noch der Wunschpfad einzutragen ist:, wobei die Angabe hier relativ zum Dokumentroot verwendet wird:  $Config['UserFilesPath'] = '/dateien/' ;

Die Angabe erfolgt relativ zum Dokumentroot. Ergebnis:

$Config['UserFilesPath'] = '/Wunschordner/' ;

Abhängig von Deiner Version musst Du eventuell  $Config['Enabled'] auf TRUE setzen 
in /FCKeditor/editor/filemanager/browser/default/connectors/php/config.php.

// SECURITY: You must explicitelly enable this "connector". (Set it to "true").
$Config['Enabled'] = true ;

(...)

Setzt außerdem die Werte  _FileBrowserLanguage and _QuickUploadLanguage  auf php  

var _FileBrowserLanguage    = 'php' ;    // asp | aspx | cfm | lasso | perl | php | py
var _QuickUploadLanguage    = 'php' ;    // asp | aspx | cfm | lasso | php

Übersetzungs-Anmerkung: das bezieht sich auf die Datei  fckconfig.js  auf oberster Ebene des FCK-Ordners

---

TEXTAREA-Methode bei PHP-Seiten-Einbindung:

Deutsche Übersetzung aus dem FCKeditor-Handbuch
 http://fckeditor.wikiwikiweb.de/Developer's_Guide/Configuration/Built_in_File_Browser

Um eine Textarea zu ersetzen, musst Du etwas Javascript im Head des HTML-Dokuments platzieren. Das folgende  Snippet enthält einige Konfigurationen, ebenso zwei Zeilen für Upload-Dateien (z.B. Bilder) . Um Bilder hochzuladen wirst einige Änderungen an einigen Dateien vornehmen, die später beschrieben werden. In diesem Beispiel habe ich PHP benutzt, um das Javascript in den HEAD der HTML-Seite zu platzieren (das erlaubt Dir, die Pfade zu den Upload-Datei-Ordnern zu setzen)

//----------------------------------
// Add jsavscript to HEAD to replace textarea with HTML editor
// The name of the textarea we want to replace is 'text_content'

// Notice that we specify a oFCKeditor.Config[\'ImageBrowserURL\'] and a oFCKeditor.Config[\'LinkBrowserURL\']
// We can dynamically assign the folders the user can look at by changing the ServerPath variable.

$server_path = BASE_PATH.'content/';
$server_path_img = $server_path.'images/';
$server_path_links = $server_path.'links/';
$server_path_flash = $server_path.'flash/';

$_js = '
<script type="text/javascript" src="fkeditor/fckeditor.js"></script>
<script type="text/javascript">
window.onload = function()
{
        var oFCKeditor = new FCKeditor( \'text_content\' ) ; // Instantiate an editor with
                                                             // the name of the TEXTAREA input.
        oFCKeditor.BasePath     = "fkeditor/" ; // This may need to change depending on the name
                                                // of the folder you have FCKeditor in.
        oFCKeditor.Height = "500"; // NOTE: do not put px, just leave the numbers as is

        // See the documentation for more parameters. Width, setToolbar etc...

        // NOTE: it is important to have the ../../ in the file path
        // There probably is a bug that needs to be fixed.
        // Also we pass the Type and the ServPath variable

       oFCKeditor.Config[\'ImageBrowserURL\'] = oFCKeditor.BasePath + \'../../filemanager/browser/default/browser.html?Connector=connectors/php/connector.php&Type=Image&ServerPath='.$server_path_img.'\';
       oFCKeditor.Config[\'LinkBrowserURL\'] = oFCKeditor.BasePath + \'../../filemanager/browser/default/browser.html?Connector=connectors/php/connector.php&ServerPath='.$server_path_links.'\';
       oFCKeditor.Config[\'FlashBrowserURL\'] = oFCKeditor.BasePath + \'../../filemanager/browser/default/browser.html?Connector=connectors/php/connector.php&Type=Flash&ServerPath='.$server_path_flash.'\';
        // This line must come in last once all the configs have been made.
        oFCKeditor.ReplaceTextarea() ;
}
</script>
';

$tpl->append('HEAD',$_js);
//--------------------------------------------


To upload files to the server you will also need to:
Um Dateien auf den Server zu laden, müsst Ihr außerdem:

1) chmod 0777 the directory you want to upload to (insecure).

      Note: It is advisable to change the group ownership of the directory to the same user as apache and add group write permisions instead

2a) in .../connectors/php/config.php You have to set $Config['Enabled'] to TRUE

2b) as well as comment the line starting with $Config['UserFilesPath'] = '...';

3) If you want to use absolute paths in the javascript snippet above you have to change .../connectors/php/connector.php

and replace: $GLOBALS['UserFilesDirectory'] = GetRootPath() . $GLOBALS['UserFilesPath'] ;

with:

$GLOBALS['UserFilesDirectory'] = $GLOBALS['UserFilesPath'] ;

4) You may also need to comment the lines in the fckconfig.js file that relate to 'ImageBrowserURL' and 'LinkBro


Dateitypen beim Upload

In .../connectors/php/config.php könnt Ihr konfigurieren, welche Dateierweiterungen beim Uplad erlaubt oder verboten sein soll.
Die Dateitypen, die man konfigurieren kann sind:
Dateien, z.B. : 'htm', 'html', 'php', 'php3', 'php5', 'phtml', 'asp', 'aspx', 'ascx', 'jsp', 'cfm', 'cfc', 'pl', 'bat', 'exe', 'dll', 'reg', 'cgi', 'asmx'
Images, e.g. : 'jpg', 'gif', 'jpeg', 'png'
Flash, e.g. : 'swf', 'fla'
Media, e.g. : 'swf', 'fla', 'jpg', 'gif', 'jpeg', 'png', 'avi', 'mpg', 'mpeg'

Denying extensions will show all files except for the ones with the specified extensions, while allowing extensions will show no files except for the ones with the specified extensions. To allow all extensions for a filetype, leave both of the arrays empty for that filetype.

---

PHP Safe Mode:

Important Note for PHP with Safe Mode activated: You'll have to create /UserFiles/File, /UserFiles/Flash, /UserFiles/Image and /UserFiles/Media in order for the filebrowser to work. Of course, you'll also have to set the correct permissions for these directories. Furthermore, don't use the "Create new folder" button. The folder would be created but couldn't be used (Safe Mode restriction).

Abweichende Konfigurationseinstellungen:

Wichtig: Bei allen Änderungen der Konfiguration den Browser-Cache löschen, da sonst die Änderungen nicht angezeigt werden!

Shortcuts zum Cache-Löschen:
Beim Internet Explorer:  STRG + F5 

Beim Fireforx/Mozialla: Umschalt+STRG+R (hilft nicht immer)

Trick: You could add a number or code in the end of the custom configuration path, so the browser would be forced to load it every time:

var oFCKeditor = new FCKeditor( "FCKeditor1" ) ;
oFCKeditor.Config["CustomConfigurationsPath"] = "/myconfig.js?" + ( new Date() * 1 ) ;
oFCKeditor.Create() ;

---

Zum Ändern der Konfiguration entweder

• die Konfigurationsdatei ändern, oder
• eine zusätzliche, eigene Konfigurationsdatei installieren (empfohlen, insbesondere bezüglich der Updates)

---

Zusätzliche Konfigurationsdatei erstellen:

1. Schritt: Eine Datei anlegen, die z.B. "myconfig.js" lautet, und irgendwo (z.B. im Rootverzeichnis) speichern.  Die vorhandene Konfigurationsdatei fckconfig.js muss vorhanden bleiben, sie darf nicht gelöscht werden.

2. Schritt: In der selbstgeschaffenen Datei die abweichenden Einstellungen notieren. Z.B., um beim Start die französische Spracheinstellung zu erzwingen:

FCKConfig.AutoDetectLanguage = false ;
FCKConfig.DefaultLanguage = "fr" ;

3. Schritt: Selbstgeschriebene Konfigurationsdatei einbinden (statt der Standard-config.js)

a) Entweder in der fckconfig.js die Einbindung der selbstgeschriebenen Konfigurationsdatei veranlassen (wirkt generell).

FCKConfig.CustomConfigurationsPath = "/myconfig.js" ;

b) Oder die fckconfig.js belassen und die Einbindung individuell in der einzelnen Seite erzwingen:

var oFCKeditor = new FCKeditor( "FCKeditor1" ) ;
oFCKeditor.Config["CustomConfigurationsPath"] = "/myconfig.js"  ;
oFCKeditor.Create() ;

Voreingestellte CSS ändern:

Inside the editor area, texts are displayed using a default css file : /editor/css/fck_editorarea.css This basic file can be over-ridden : just change the value of the FCKConfig.EditorAreaCSS key in the main fckconfig.js (or your own) configuration file. 

---

Toolbar anpassen

The editor comes with the "Default" and "Basic" toolbarsets already defined in the fckconfig.js file. You can modify them, but you can also create new customized ones. For example, to create a toolbarset named "MyToolbar", just include the following in the configuration file:

FCKConfig.ToolbarSets["MyToolbar"] = [
        ['Cut','Copy','Paste','PasteText','PasteWord'],
        ['Undo','Redo','-','Bold','Italic','Underline','StrikeThrough'],
        '/',
        ['OrderedList','UnorderedList','-','Outdent','Indent'],
        ['Link','Unlink','Anchor'],
        '/',
        ['Style'],
        ['Table','Image','Flash','Rule','SpecialChar'],
        ['About']
] ;

Now you just need to set your toolbarset when creating an editor instance. For example, with JavaScript you would do something like this:

<script type="text/javascript">
        var oFCKeditor = new FCKeditor( 'FCKeditor1' ) ;
        oFCKeditor.ToolbarSet = 'MyToolbar' ;
        oFCKeditor.Create() ;
</script>

---

Snippet für ein Auswahlfeld für die verschiedenen Toolbar-Versionen:

Im Head:
 <script type="text/javascript">
function FCKeditor_OnComplete( editorInstance )
{
    var oCombo = document.getElementById( 'cmbToolbars' ) ;
    oCombo.value = editorInstance.ToolbarSet.Name ;
    oCombo.style.visibility = '' ;
}
function ChangeToolbar( toolbarName )
{
    window.location.href = window.location.pathname + "?Toolbar=" + toolbarName ;
}
</script>

Im Body an gewünschter Stelle:<select id="cmbToolbars" onchange="ChangeToolbar(this.value);" style="VISIBILITY: hidden">
<option value="Default" selected>Default</option>
<option value="Basic">Basic</option>
</select>

---

Die vorgegebenen Toolbar-Varianten "Default" und "Basic" in der fckconfig.js:

FCKConfig.ToolbarSets["Default"] = [
        ['Source','DocProps','-','Save','NewPage','Preview','-','Templates'],
        ['Cut','Copy','Paste','PasteText','PasteWord','-','Print','SpellCheck'],
        ['Undo','Redo','-','Find','Replace','-','SelectAll','RemoveFormat'],
        ['Bold','Italic','Underline','StrikeThrough','-','Subscript','Superscript'],
        ['OrderedList','UnorderedList','-','Outdent','Indent'],
        ['JustifyLeft','JustifyCenter','JustifyRight','JustifyFull'],
        ['Link','Unlink','Anchor'],
        ['Image','Flash','Table','Rule','Smiley','SpecialChar','UniversalKey'],
        ['Form','Checkbox','Radio','TextField','Textarea','Select','Button','ImageButton','HiddenField'],
        '/',
        ['Style','FontFormat','FontName','FontSize'],
        ['TextColor','BGColor'],
        ['About']
] ;

FCKConfig.ToolbarSets["Basic"] = [
        ['Bold','Italic','-','OrderedList','UnorderedList','-','Link','Unlink','-','About']
] ;

---

Lösung für die Pfadprobleme beim Bildupload und Bild-Serverdurchsuchen (Bild-Browser)

Quelle: http://phiyan.hollosite.com/

For PHP ONLY! If there are any problems, questions, or fixes for other connections and such
E-Mail: phiyan@gmail.com

In connector.php, look for this group of lines:

if ( isset( $Config['UserFilesPath'] ) )
$GLOBALS["UserFilesPath"] = $Config['UserFilesPath'] ;
else if ( isset( $_GET['ServerPath'] ) )
$GLOBALS["UserFilesPath"] = $_GET['ServerPath'] ;
else
$GLOBALS["UserFilesPath"] = '/UserFiles/' ;

Go to the else command, and change the '/UserFiles/' to your desired directory.

If you do not want to have FCKEditor create a folder based on the mime type (the Image Folder,
for example, when you you upload an Image).
Then open up io.php file, and look for this group of lines:

$sResourceTypePath = $GLOBALS["UserFilesDirectory"] . $resourceType . '/' ;

// Ensure that the directory exists.
CreateServerFolder( $sResourceTypePath ) ;

// Return the resource type directory combined with the required path.
// return $sResourceTypePath . str_replace( '/', '\\', RemoveFromStart( $folderPath, '/' ) ) ;
return $sResourceTypePath . RemoveFromStart( $folderPath, '/' ) ;

Change the $sResourceTypePath value to: $GLOBALS["UserFilesDirectory"] ;
So you should then have:

$sResourceTypePath = $GLOBALS["UserFilesDirectory"] ;

And then to correctly use pictures with the browser, go to frmresourceslist.html. Then go
through the JavaScript and find this line:

var sCurrentFolderUrl = oNode.attributes.getNamedItem('url').value ;

Now add this(these) line below it, depending on what file types you are using:

sCurrentFolderUrl = sCurrentFolderUrl.replace("Image/", "");
sCurrentFolderUrl = sCurrentFolderUrl.replace("Media/", "");
sCurrentFolderUrl = sCurrentFolderUrl.replace("File/", "");
sCurrentFolderUrl = sCurrentFolderUrl.replace("Flash/", "");

This is a bad fix, so if someone who has more experience with JavaScript and XML
is willing to explain to me what is going on or wants to create a better fix, tell me.

---

Bei Verwendung von Firefox ergeben sich gelegentlich Probleme oder unterschiedliche Verhaltensweisen zum IE, so z.B. beim Einfügen von <p> statt <br> beim Drücken der Entertaste (wieder unterschiedlich zur Kombination Shift-Enter), oder das Zeichenformatieren eine ganzen Wortes, wenn der curser irgenwo im Wort steht (scheint nur unter IE zu funktionieren); ferner die automatische Linkersetzung (scheint ebenfalls nur unter IE zu funktionieren).

Hier ein Hinweis zu folgenden zwei Problemen:

• Beim Rechtsklick kein Kontextmenü zum Kopieren und Einfügen
• Nachträgliches Tabellen-Editieren funktioniert nicht

Ein nur scheinbarer Unterschied ist der Umstand, dass bei Firefox beim Rechtsklick kein fck-kontextmenü erscheint, beim IE schon.
Damit ist auch das nachträgliche Editieren von Tabellen und Tabellenzellen  in fckeditor unmöglich (der Linksklick auf das Tabellesymbol erlaubt nur eine neue Tabelle), da das entsprechende Kontextmenü nicht erscheint (sondern nur das allgemeine Firefox-Kontextmenü).

Ursache ist aber eine Javascript-Einstellung im Firefox.


Bei der Suche ähnlicher Probleme empfehle ich, zuerst die Beiträge in der
Projektseite/Bugs:


zu Rate zu ziehen, ferner die Projekt-Forums-Seiten

Auf der Original-sourceforge-Projektseite des fckEditors findet man eine Liste von PLUGINS zum fckEditor, und zwar auf


Hier ein Auszug aus der Liste:

Request ID	Summary	Open Date
1590013	MODx site link plugin	2006-11-03 08:13
1588968	<abbr>-tag	2006-11-01 15:53
1581776	Realtime Spellchecker (Firefox 2.0)	2006-10-21 03:56
1549925	AA Inline Style Editor	* 2006-08-31 06:22
1534632	EasyUpload plugin	* 2006-08-04 08:31
1525432	kfm 0.4 - kae's file manager	* 2006-07-19 10:02
1512825	Custom Characters plugin	* 2006-06-26 09:23
1511556	AJAX Save Plugin and CTRL+S save option	* 2006-06-23 13:33
1510783	EmbedMovies	* 2006-06-22 09:24
1510662	CharsCounter (and MaxLength) plugin(VER 2.3 fix)	* 2006-06-22 07:04
1496120	Custom XML tags support and Locked regions	* 2006-05-27 12:30
1496112	BiDi support	* 2006-05-27 11:46
1496110	serverPreview: process the preview at the server	* 2006-05-27 11:37
1490723	Formula Editor Plugin	* 2006-05-18 00:36
1487906	Maximize In Dialog	* 2006-05-13 06:29
1469969	eZ Publish Integration	* 2006-04-13 10:51
1469494	Non-breaking Space Plugin	* 2006-04-12 13:35
1466737	Social Bookmarks for FCKeditor	* 2006-04-07 23:16
1456214	ImageManager Plugin for FCK	* 2006-03-22 07:54
1455334	extended nodepath	* 2006-03-21 04:31
1448301	dynamic CSS Plugin	* 2006-03-12 05:50
1442286	Combo plugin	* 2006-03-02 23:27
1431377	DHTML-Comment-Boxes/-Info-Boxes	* 2006-02-14 03:05
1431373	Convert Tab-Stops from Word-Text	* 2006-02-14 02:44
1431361	stripTags-Plugin	* 2006-02-14 02:19
1425118	iBrowser	* 2006-02-06 02:34
1409213	Local Storage for values	* 2006-01-18 09:09
1403818	CharsCounter (and MaxLength) plugin	* 2006-01-12 04:05
1396390	Snippets	* 2006-01-03 15:14
1390968	Sample OnKeyDown Event Capture Plug-in	* 2005-12-26 18:00
1389555	Content Max Length for editor	* 2005-12-24 05:35
1383674	Tagging Plugin	* 2005-12-17 08:44
1355178	Path to current node	* 2005-11-12 06:18
1342783	ChangeHeading	* 2005-10-30 13:18
1328569	required form elements	* 2005-10-17 04:08
1326137	proIframe 1.0	* 2005-10-13 12:42
1324779	HtmlTiles Plugin 1.0	* 2005-10-12 05:04
1315686	iBrowser V 1.31 released!	* 2005-10-07 02:17
1286252	Open in new window V2	* 2005-09-09 11:50
1278606	'CMS Made Simple' Content browser/insert link	* 2005-09-01 02:41
1274337	SpellWord-plugin	* 2005-08-26 15:39
1269447	OpenWord-plugin	* 2005-08-24 15:22
1236692	Open in new window	* 2005-07-12 06:15
1230849	Template Manager v1.0	* 2005-07-01 03:06
1218212	iManager V 1.1 released	* 2005-06-10 06:30
1216783	Cross-browser toggle table borders plugin	* 2005-06-07 17:14
1209898	FileIcon	* 2005-05-27 07:20
1209888	Flash plugin v2	* 2005-05-27 07:13
1209171	iManager V 1.0 beta released	* 2005-05-26 07:08

1208017	Flash Plugin	* 2005-05-24 10:52
1207844	Flash Plugin for FCK2.0-FC	* 2005-05-24 07:28
1204026	Plugin : SpanControl	* 2005-05-17 19:22
1202718	iBrowser V 1.1 released	* 2005-05-16 02:04
1188595	HTML CleanUp Plugin	* 2005-04-23 07:52
1173310	Plugin: Content length toolbar button	* 2005-03-30 05:53

FCKEditor läuft unter IE 5.5+ (Windows), Firefox 1.0+, Mozilla 1.3+ and Netscape 7+.

Safari-User haben Probleme mit dem FCK-Editor. Offiziell unterstützte bisher der  FCK-Editor den Safari-Browser überhaupt nicht,  da jener durch interne Limitationen die Funktionalität verhinderten. Mittlerweile gibt  es gesonderte Anstrengungen, hier doch noch eine Kompatibilität zu erreichen, wobei es (Stand April 2007) offenbar erste Erfolge gibt. Notwendig scheint aber die neueste Safari-Version zu sein.

Die FCKEditor-Homepage betreibt eine eigene Seite zu diesem Projekt:


Ein weiteres Problem beim Safari scheint zu sein, dass dieser - auch in den neueren Versionen - immer noch erhebliche Bugs enthält, die den FCKeditor-Programmierern Schwierigkeiten machen. So wären zwei Versionen denkbar: eine (auf Safari) stabile FCKEditor-Version mit eingeschränkter Funktionalität und eine unsichere Version, die in Einzelfällen unter Safari versagt. Da der Editor unter allen Browser laufen muss, kann nur eine FCKEditor-Version programmiert werden, und den Editor wegen der Safari-Schwächen in der Entwicklung hintan stehen zu lassen und die Low-Version zu veröffentlichen, schied verständlicherweise aus.

Mac-User:

Für Mac-User gibt es noch die Ausweichmöglichkeit, Mac-Firefox oder Camino zu verwenden!

Auf den Webseiten  http://www.saulmade.nl/FCKeditor  findet man

• Skins,
• Plugins und
• PHP-Snippets

von Paul Moers, einem der Macher von FCKEditor.

HOWTO -Get absolute urls with the filemanager By: saul11 (saul11) - 2006-11-24 09:10

Just open the 'frmresourcelist.html' file of the filemanager (/FCKeditor/editor/filemanager/browser/default/frmresourceslist.html)  and change line 66 :  var sLink = '<a href="#" onclick="OpenFile(\'' + fileUrl + '\');return false;">' ;  into :  var sLink = '<a href="#" onclick="OpenFile(\'' + top.opener.document.location.protocol + '//' + top.opener.document.location.host + fileUrl + '\');return false;">' ;    By doing this you prepend the adres to your FCKEditor to the relative path.

Correction - Get absolute urls with the filem By: saul11 (saul11) - 2006-11-25 03:27

The code should be     // Build the link.  fileUrl = top.opener.FCKConfig.FullBasePath.substr(0, top.opener.FCKConfig.FullBasePath.length - top.opener.FCKConfig.BasePath.length) + fileUrl;  var sLink = '<a href="#" onclick="OpenFile(\'' + fileUrl + '\');return false;">' ;    The code I posted earlier only appends the protocol, server name, subdomain, and domain name to the relative url. So if your editor is not in your webserver root directory this won't work. the above code fetches the absolute url to your FCKeditor and appends it to the relative path of the files. Resulting in an absolute path for the files.

HOWTO - Get absolute urls with the LFO By: saul11 (saul11) - 2006-11-25 03:31

For the LFO plugin (http://fckplugins.saulmade.nl/ - LFO panel) you'll have to check whether the filemanager has been opened for loading a file. Loading a file should never make the URL absolute because the connector won't be able to work with it:    // Build the link.  if (!top.opener.GetFileContentsCallBack)  {  fileUrl = top.opener.FCKConfig.FullBasePath.substr(0, top.opener.FCKConfig.FullBasePath.length - top.opener.FCKConfig.BasePath.length) + fileUrl;  }  var sLink = '<a href="#" onclick="OpenFile(\'' + fileUrl + '\');return false;">' ;      The 'GetFileContentsCallBack' fcuntion is specific for the 'open file' dialog. Make the url absolute only if it's not available in the opener dialog.