Opened 12 years ago

Closed 12 years ago

#1626 closed Bug (fixed)

ASP.NET : The connector must have a full configuration file

Reported by: Frederico Caldeira Knabben Owned by: Frederico Caldeira Knabben
Priority: Normal Milestone: FCKeditor.Net 2.5
Component: Server : ASP.Net Version: SVN (FCKeditor) - Retired
Keywords: Cc:

Description

As all the other connectors, the ASP.NET implementation must provide an easy way to configure to enable and configure the connector. This is a requirement for our Server Side Integration standards.

Attachments (2)

1626_FCKeditor.patch (1.5 KB) - added by Frederico Caldeira Knabben 12 years ago.
First patch proposal for the FCKeditor repository
1626_FCKeditor.Net.patch (2.5 KB) - added by Frederico Caldeira Knabben 12 years ago.
First patch proposal for the FCKeditor.Net repository

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by Frederico Caldeira Knabben

Attachment: 1626_FCKeditor.patch added

First patch proposal for the FCKeditor repository

Changed 12 years ago by Frederico Caldeira Knabben

Attachment: 1626_FCKeditor.Net.patch added

First patch proposal for the FCKeditor.Net repository

comment:1 Changed 12 years ago by Frederico Caldeira Knabben

Keywords: Discussion added

I've attached a first proposal way to handle this thing. Both the FCKeditor and the FCKeditor.Net repositories must be patched though.

The idea is having the settings in the config.ascx file. Developers will be able to change the settings by simply editing that file, without having to recompile anything, not even make changes to the Web.config. This solution should make it possible to also include custom code in the configuration, to handle any kind of need in this sense, like getting settings from the session or even from the database.

I'll be waiting for comments on this, to check if this is really the way to go.

comment:2 Changed 12 years ago by Frederico Caldeira Knabben

Talking with Alfonso, we have found that the proposed system must have further enhancements:

  • Possibility of defining a custom configuration object that can be available in the session or application environment. If available, the config.ascx file is ignored.
  • Possibility of overriding the settings through the web.config file, by using the appSettings. The keys must be composed by the "FCKeditor:Connector:" prefix, plus the setting name. For example: FCKeditor.Connector:Enabled and FCKeditor.Connector:AllowedExtensions:File. The old "FCKeditor:UserFilesPath" must still be used, but deprecated in favor of "FCKeditor:Connector:UserFilesPath".

comment:3 Changed 12 years ago by Frederico Caldeira Knabben

The configuration loading must be done in the following order (each step pass to the next one if not defined):

  1. Session
  2. Application
  3. Web.config
  4. config.ascx

comment:4 Changed 12 years ago by Frederico Caldeira Knabben

Ok, I've attached two new patches to #79. It includes not only configuration file things, but also other general things.

We are now the advanced features described in my previous comment to CKFinder. The proposed patches add the config.ascx file, but still uses the "FCKeditor:UserFilesPath" feature in the web.config, session and application. So, it adds to the current features, but don't remove anything we have today.

I'll be closing this ticket as soon as the patch gets committed at #79.

comment:5 Changed 12 years ago by Frederico Caldeira Knabben

Keywords: Discussion removed
Resolution: fixed
Status: newclosed

Fixed with [1202] and [1203].

Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy