FckEditor validation

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
2/10/2008 1:03:31 AM
Gravatar
Total Posts 18

FckEditor validation

Hi Joe,

I was wondering if you've successfully done client-side validation (e.g. via custom validator) on FckEditor fields in mojoPortal?  If so, do you have code snippets or can you point me to where you've used them.

Thanks in advance,

Sherwin

2/17/2008 10:20:26 AM
Gravatar
Total Posts 18439

Re: FckEditor validation

Hi Sherwin,

Sorry but I have not had a need for client side validation or server side validation in the editor. Given that the editor is for entering free form html content, the only kind of validation I can think of is html validation but the editor does a pretty good job of that unless someone is trying to enter invalid content. For untrusted content such as in public forums and blog comments we don't worry about validating content on the way into the db, but we treat it as untrusted content coming from the db and we prevent malicious or invalid content from rendering using NeatHtml.

The only cases where I see invalid content entering the system from trusted users is when they copy paste something invalid from Word or some other source, but these issues are best mitigated by training the users to use the "Paste As Text" or "Paste From Word" toolbar items in the editor. In the forums I have forced "Paste As Text" because people often paste errors they have copied from rendered html and frequently they miss an opening or closing tag due to the way the copy it.

Best Regards,

Joe

You must sign in to post in the forums. This thread is closed to new posts.