Using DotNetNuke 4.5.1 w/ FCKeditor 2.4.1, I woud like to restrict the Fonts allowed, to make available only Verdana (and have Verdana be the default, of course). Would someone please suggest how I might do this? Thank you.

Thank you, Locopon. Your provided very detailed instructions, bringing me right to a solution.

However, I find that your option #1 below is not changing the FCKeditor Font list. After I make the change you recommend, leaving only the font 'Verdana" in the FCKConfig.FontNames setting, the Font list still shows all the original fonts (Arial, Comic Sans, Courier New, Tahoma, Times New Roman, Verdana). I even cleared my IE7 cache,  restarted the application, and rebooted the server, but still - no change to the Font list.

And because you provided clear instructions for a resolution, I also found the fckconfig.js located in:

\Providers\HtmlEditorProviders\FckhtmlEditorProvider\FCKeditor

.. and changed the FCKConfig.FontNames setting, (just incase) removing all but the Verdana font, and still all the fonts show in the Font dropdown list when using the editor.

I also made your option #2 'default font' change by modifying the body { } selector in the file:

Providers\HtmlEditorProviders\Fck\FCKeditor\editor\css\fck_editorarea.css

from:

body, td
{
 font-family: Arial, Verdana, Sans-Serif;
 font-size: 12px;
}

to:

body, td
{
 font-family: Verdana, Sans-Serif;
 font-size: 12px;
}

... just incase this #2 option was needed, too. Still, all the default fonts are showing in the Font dropdown list.

Am I missing a step somewhere?

Thank you for pointing out the definition of the FCKeditor in the web.config file. I am happy to say - you are correct - your suggestion above work perfectly!

I was mistakenly making your suggested changes under:

Providers\HtmlEditorProviders\FckhtmlEditorProvider\Custom (wrong)

instead of:

Providers\HtmlEditorProviders\Fck\Custom (correct!)

Once I saw the Providers\HtmlEditorProviders\Fck\Custom path in the web.config file, I could see my mistaken oversight.

Thanks very much, Locopon, for following up with this thread until I could implement your original instructions correctly.