Java Connector parameter

Hi, Im using FCKeditor with the java integration pack. I need to be able to pass addtional parameters (request.getParameter) to the connector servlet when a user uploads a file but have no idea how to accomplish this. The parameter name will be consistent throughout although the value will be generated on the jsp page where the editor is shown (using the jsp tags provided with the inetegration pack).

Im looking for the place where the connector url is contructed inorder to pass a new parameter (i.e ?id=21) to the end of the url. i was hoping a specify an attribute in the jsp tags to hold the name and value and use that somewhere to construct the parameter.

Any Ideas?

Cheers, Ry

Mon, 04/06/2009 - 22:37

mosipov

Joined: 22/02/2008

Posts: 574

Re: Java Connector parameter

Check this thread, viewtopic.php?f=6&t=11290&hilit=+rewrite

Might help you.

Wed, 04/08/2009 - 18:30

ryanlane

Joined: 06/04/2009

Posts: 2

Re: Java Connector parameter

mosipov wrote:Check this thread, viewtopic.php?f=6&t=11290&hilit=+rewrite

Might help you.

Just to confirm then, in the FCK tags in the jsp filr, this is legal, rather that obtaining the url from the config js file?

<FCK:editor instanceName="blog" basePath="/scripts/fckeditor" height="400px" toolbarSet="blog">
        <jsp:attribute name="value" trim="true">${entity.blog}</jsp:attribute>
         <FCK:config ImageBrowserURL="all-the-normal-uoload-url + ?type=blog"/>
</FCK:editor>

and then my imeplemntation of the userpathbuilder (although unrelated to the user in my case) will be

public String getUserPath(HttpServletRequest request) {
String newParameter = request.getParameter("type");
//build path here
}

so that the type string will now hold the value 'blog' correct?

Many thanks

Thu, 04/09/2009 - 19:10

mosipov

Joined: 22/02/2008

Posts: 574

Re: Java Connector parameter

Hi Ryan,

ryanlane wrote:
mosipov wrote:Check this thread, viewtopic.php?f=6&t=11290&hilit=+rewrite

Might help you.

Just to confirm then, in the FCK tags in the jsp filr, this is legal, rather that obtaining the url from the config js file?

It's perfectly legal. You are allowed to pass anything through FCK:config which complies to the editor. There is one thing though you should know: The difference between config.js and FCK:config => config.js is valid for all FCKeditor instances from the same basepath in contrast to FCK:config dynamically overrides config options for the current instance only.

If you think, your param is worth to be global, make it global in the config.js.

ryanlane wrote:

<FCK:editor instanceName="blog" basePath="/scripts/fckeditor" height="400px" toolbarSet="blog">
        <jsp:attribute name="value" trim="true">${entity.blog}</jsp:attribute>
         <FCK:config ImageBrowserURL="all-the-normal-uoload-url + ?type=blog"/>
</FCK:editor>

You can even do better:

<FCK:editor value="${entity.blog}" instanceName="blog" basePath="/scripts/fckeditor" height="400px" toolbarSet="blog">
         <FCK:config ImageBrowserURL="all-the-normal-uoload-url + ?type=blog"/>
</FCK:editor>

There is another catch with the config.js: It is completely client-side, which means you cannot pass any dynamic params whereas FCK:cofig gives that possibility:

<FCK:editor value="${entity.blog}" instanceName="blog" basePath="/scripts/fckeditor" height="400px" toolbarSet="blog">
         <FCK:config ImageBrowserURL="all-the-normal-uoload-url + ?type=${uploadType}"/>
</FCK:editor>

ryanlane wrote:
and then my imeplemntation of the userpathbuilder (although unrelated to the user in my case) will be
public String getUserPath(HttpServletRequest request) {
String newParameter = request.getParameter("type");
//build path here
}
so that the type string will now hold the value 'blog' correct?

Many thanks

Basically yes, but pay attention ImageBrowseURL != ImageUploadURL, check the docs one more time.

I am glad, I could help,

Mike

EDIT: Just editor my config.js from

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

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

and the request contained this parameter too.