fckeditor

Usually, you do not want websites that are still under development to be visible to the Web at large. Even if you do not care about that, at the least - you do not want such websites to be indexed by search engine bots. Bottomline - you want the "dev" websites behind a lock. One way to secure, is to restrict IP addresses, but then - that is so '90s! In the modern world we are way too mobile, for such approaches. They will just add annoyance and stand in the way of productivity. If you are using Drupal, one solution is to use the Securesite module. Or maybe not. In a busy development shop you usually deal with a dozen of under-the-development projects and triple that amount of projects that you maintain, hence still have dev environments for. Maintaining Securesite for each one of them is a maintenance nightmare. Please note, we are not even mentioning how buggy Securesite is and how it conflicts every time you try to do something advanced. Where I work, we chose a parsimonious approach.

It's official - we are migrating to FCKeditor

A WYSIWYG HTML editor is a necessary part of any Web-based, CMS system. You simply can not expect user audience to be fluent in HTML.

We've been using TinyMCE with IMCE (for image upload), in all our Drupal installations, for a long time now. About 2 years ago we did comparison of TinyMCE vs FCKeditor and Tiny came up as an undoubted winner. However, it's far from flawless and during these years, we've had loads of headache dealing with its bugs and frustrated users.

Recently, we re-visited our WYSIWYG editor policy and noticed that FCKeditor has come a very long way during last year. We installed it and immediately saw huge difference in both stability, as well as user-friendliness.

We've been using FCKeditor on some of our Drupal installations for some time, now and today we made a final decision to migrate all our installations to FCKeditor. We are using the latest stable release: 2.4.3. We tried the beta release of 2.5.x because this is the first version that supports Safari browser, but unfortunately it's still too buggy for production use (or Drupal integration is). Hopefully, 2.5 will mature soon, since we are very eager to add Safari support.