Troubleshooting

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

To get round the 'RequiredFieldValidator' problem in .NET, I found the following solution:

Add a JavaScript function to the page:

   function FCK_ValidationFix()
   {
        if (FCKeditorAPI && FCKeditorAPI.Instances)
        {
           for (var i in FCKeditorAPI.Instances)
            {
            var anFCK = FCKeditorAPI.Instances[i];
            anFCK.UpdateLinkedField();
            }
        }
   }

To the 'insert' button on the form, add ' OnClientClick="FCK_ValidationFix()" '. This function gets called before ASP.NET's webform validation stuff and ensures that the FCK's hidden input is populated before validation takes place. Then the regular RequiredFieldValidator appears to work just fine.

I've only just discovered this so there may be a good reason why this is a bad idea (also I presume the UpdateLinkedField gets called before submit as well which is redundant). If whoever reads this thinks it's OK, perhaps you'd like to copy it to the content page (which I can't edit as it's locked).

-- Danielrendall

This page was last edited on 22 July 2008, at 13:14.