Hi.
I'm under huge pressure to get a web based editor up and running in a classic asp site. This looks like just the solution, my concern is that I might be 3 weeks down the line of implementing it into the production environment only to find that there are some issues with it that are insurmountable. I'm hoping that some kind people might be able to validate that it is a good choice (or indeed the right/best choice) for the following:
- I want to be able to sit the editor within a page of the asp classic website
- I need to be sure that it is secure - the editor would need to be able to check if the user has a valid logged in session as created upon login to the application
- I need to be sure that the result of the edited text is downloadable as a word document or rich text document so that the client user can save the document up to the server
I'm going to go ahead and download and start playing around with it, but if anyone can provide experience in implementing it in classic asp, or do's/dont's or warnings etc I would appreciate it hugely. Any feedback welcome, particularly with respect to asp classic implementation.
Thanks.
I'm under huge pressure to get a web based editor up and running in a classic asp site. This looks like just the solution, my concern is that I might be 3 weeks down the line of implementing it into the production environment only to find that there are some issues with it that are insurmountable. I'm hoping that some kind people might be able to validate that it is a good choice (or indeed the right/best choice) for the following:
- I want to be able to sit the editor within a page of the asp classic website
- I need to be sure that it is secure - the editor would need to be able to check if the user has a valid logged in session as created upon login to the application
- I need to be sure that the result of the edited text is downloadable as a word document or rich text document so that the client user can save the document up to the server
I'm going to go ahead and download and start playing around with it, but if anyone can provide experience in implementing it in classic asp, or do's/dont's or warnings etc I would appreciate it hugely. Any feedback welcome, particularly with respect to asp classic implementation.
Thanks.
Re: Implement in Classic ASP
2. Uh, that's your job. This isn't a CMS, just a little widget.
3. Also this is your job, as you can read everywhere, FCKeditor is a XHTML editor, if you want to use other formats that's up to you to convert from/to XHTML.