Should be easier to pass parameters to connector

[farmerzen]

A nice to have would be an easy way to pass parameters to the connector URL, without having to worry with connector link and parameters encoding!

[Michael Osipov]

Based on this ​thread.

[Alfonso Martínez de Lizarrondo]

The javascript integration already takes care of calling encodeURIComponent to encode the parameters to the connector, so this is only an issue with the java integration that isn't providing a system to help this situation.

FCKConfig.ImageBrowserURL = FCKConfig.BasePath + 'filemanager/browser/default/browser.html?Type=Image&Connector=' + encodeURIComponent( FCKConfig.BasePath + 'filemanager/connectors/' + _FileBrowserLanguage + '/connector.' + _FileBrowserExtension ) ;

[Michael Osipov]

This is not what the ticket is about. The OP wants to pass certain parameters to every FCKeditor instance at load time. They will be used in the connector. There is only one cumbersome way thrugh the *BrowserURL modification.

A Config param like FCKConfig.AdditionalConnectorParams = {param1: "value", param2: "value2"}. Would be more helpful for every connector.

[Frederico Caldeira Knabben]

Good idea. But note that the editor is not aware about the existence of "connectors". It just have URLs pointing to file browsers and uploaders. It could even be pointed to a plain HTML page, with no URL parameters at all.

In any case, as we're offering an integrated solution by default, it would not be wrong to offer s simple function to help with these settings. Something like this:

FCKConfig.ImageBrowserURL = FCKConfig.FileBrowserUrl( _FileBrowserLanguage, 'Image',
    {
        param1 : 'value1',
        param2 : 'value2'
    } ) ;

It would pass "param1" and "param2" straight to the connector.

[Jakub Ś]

FCKeditor was retired and is no longer supported. All active development was moved to its successor, ​CKEditor 3.x, that is a fully mature and far superior product. We recommend you upgrade as soon as possible.