I've finally managed to upgrade to the latest blog module and have immediately run into a problem.

The last Blog release I was using (3.3.1) had a plain text area for the summary field. The new release has the rich text editor there instead. Because of the way FCK works, this means that the function to generate the summary from the post's body content no longer works.

I'm looking for a good workaround. Not one that replaces paragraphs with divs or breaks (The enter key is supposed to generate paragraphs), not one that removes the character inside the paragraph (authors expect repeat paragraphs to create gaps), and not one that involves an unintutive operation like switching to source or text view and clearing it before updating (big fail).

The most effective workaround would be if I could restore the editor to be plain text by default.

With that in mind I've used the information on this page:
http://www.dotnetnuke.com/Development/ReleaseManagement/Roadmap/RichTextEditor/tabid/632/Default.aspx
and added DefaultMode="Basic" to the dnn:texteditor tag in EditEntry.ascx

However, I find that this doesn't work.The editor still loads in Rich text mode.

Does anyone else have any idea how to force it to text mode, or even replace the texteditor with a textarea or something?

Regards,
Rob