Ticket #79 (closed Task: fixed)

Opened 3 years ago

Last modified 2 years ago

ASP.Net integration must be comformant with our standards

Reported by: FredCK Owned by: FredCK
Priority: Normal Milestone: FCKeditor.Net 2.5
Component: Server : ASP.Net Version:
Keywords: Cc:

Description

The ASP.Net must be compliant with the minimum requirements, as defined in the Server Side Integration Status page.

Attachments

79_FCKeditor.patch Download (6.9 KB) - added by fredck 2 years ago.
Patch 1/2 (FCKeditor trunk)
79_FCKeditor.Net.patch Download (49.4 KB) - added by fredck 2 years ago.
Patch 2/2 (FCKeditor.Net trunk)

Change History

Changed 3 years ago by FredCK

  • milestone changed from FCKeditor 2.5 to FCKeditor.Net 2.3

Changed 2 years ago by fredck

FCKeditor.IsCompatibleBrowser introduced with [79].

Changed 2 years ago by fredck

Sorry... FCKeditor.IsCompatibleBrowser introduced with [1161].

Changed 2 years ago by fredck

As of [1162], the BasePath property defaults to "/fckeditor/".

Changed 2 years ago by fredck

The CreateHtml function has been introduced with [1165].

Changed 2 years ago by fredck

Patch 1/2 (FCKeditor trunk)

Changed 2 years ago by fredck

Patch 2/2 (FCKeditor.Net trunk)

Changed 2 years ago by fredck

I've attached two patches. It introduces many of the necessary features for FCKeditor.Net, including the security checks and the configuration file (fixing #1626).

Changed 2 years ago by fredck

The proposed patches "forces" us to release FCKeditor 2.5.1, which should include just the changes in "editor/filemanager/connectors/aspx". We could also consider adding other fixes, but with a lot of attention to not break anything, as this release will not pass throw the usual testing phase.

Changed 2 years ago by fredck

The proposed patches have been committed with [1202] and [1203].

Samples have been completed with [1199] and [1201].

We should be close to close this ticket.

Changed 2 years ago by fredck

  • status changed from new to closed
  • resolution set to fixed

All pending things have been coded.

Note: See TracTickets for help on using tickets.