Alrighty...we have an explanation for what the problem is with the Content Editors and Safari (issue relates to Opera as well as many other browsers).
Note: I have an explanation...not a solution...
It seems that when Telligent reprogrammed Community Server as the new version we're running CS2007.1 (aka CS 3.1) they:
"[E ]xplicitly remove support for Safari and Opera from TinyMCE because of issues we encountered with TinyMCE and the then-current versions of these browsers." according to one of their developers.
Webmaster has indeed found that there is code which checks for what browser you're running and disables the [TINYMCE] content editor completely if your browser "isn't supported".
However we're also told by Telligent that: "Safari 3.0 and Opera 9.5 greatly improve support for rich text editing, so it should be possible to support rich text editing in these browsers in the next version of CS."
Which means either Webmaster or I would need to find a way to re-enable the content editors for all browsers (by reprogramming that part of the Community Server source) or wait for the next upgrade to CS to fix this issue.
This also means that currently, if you are running Safari, Opera, or any other browser that the
Community Server [TINYMCE] software "doesn't support for rich content editors" you will only be able to post using a standard HTML multi-line text box. This text box has no automatic formatting, and you must code your own HTML tags into posts to realize line and paragraph breaks, and any other formatting.
We realize that this is a poor situation and will work to correct it as soon as is possible. Though it is entirely possible we'll need to wait for the official CS service pack upgrade to improve the functionality in this area. Until that time the only thing we can recommend is that you use either FireFox or Internet Explorer as they seem to be "supported" for rich content editing functionality at this time. We will let you know if / when this situation changes.
Therefore I apologize to any and all users who's browser preference is causing them "Pain at the Post", it is not something we did intentionally, in fact we were unaware of this issue ourselves.
Furthermore this also proves that issue does not lie with either Safari or Opera as I had originally assumed, namely because Safari and Opera DID partially support TinyMCE and FreeTextBox3 (and other) editors in previous versions of Community Server.
I had no idea that Telligent would have flat out disabled rich content editor support for certain browsers in the most recent software version. I belive this to be a poor business decision on their part. The ability to disable content editors by browser type should have been a configuration setting we (customers installing their software) could modify not a hard coded default setting.
ONLY TINYMCE DISABLES ITSELF IN SAFARI AND OPERA. COMMUNITY SERVER DOES NOT CONTAIN CODE THAT DISABLES CONTENT EDITORS OTHER THAN TINYMCE IN SAFARI AND OPERA.