I want to add basic WYSIWYG functionality to Drupal 6. It does not have to be bleeding edge.
I have found about 150 blogs and posts with options and an equal about of issues and problems
Can somebody point me to the easiest solution?
Easiest solution IMO is to use the WYSIWYG api to include TinyMCE.
You will need:
WYSIWYG dev release (supports new TinyMCE)
TinyMCE main package
The WYSIWYG module has an excellent administration screen to which you can turn buttons on and off with a simple tick box. I also prefer TinyMCE due to it's small library and therefore fast speed on browsers.
For file uploading and integration with the WYSIWYG, I use:
IMCE
IMCE Wysiwyg bridge
Which I find super easy, and business users seem to have no issues either. Supports image resizing and thumbnail generation
FCKeditor has been deprecated in favor of CKEditor. CKEditor also has a pay-for file manager addon called CKFinder.
CKEditor is a good choice. CKEditer can integrate with IMCE for file uploading as well as CKFinder.
FCKeditor and TinyMCE are both good, simple choices.
I finally got it working with this combination of modules.
TinyTiny MCE – text editor
Tiny MCE - js
IMCE – image uploader
I had a good blog with the recipe for setup, but can't find it today. :(
Related
Searching about options page, I found a lot of themes that uses a options theme page like this one:
There is an pre-built option? What framework do you advise?
Thanks
If you're not a fan of plugins go with these two options, where you can place the files within your theme and a options panel will appear. I have listed two very good ones that alot of developer use. Also there are many open source option frameworks but they're not as documented.
Option Theme Framework
Propanel
Have a look at the Options Tree plugin for this.
http://www.wordpress.org/extend/plugins/option-tree/
It's very good, easy to customise via an XML file that you load in and also easy to style the panel so your client feels like they've got a fully customised options panel put together just for them.
There is also a media uploader built in, very handy for a gallery tab.
NHP is a powerful one, but it just merged with ReduxFramework to make it even more powerful. Give it a go.
http://wordpress.org/plugins/redux-framework/
What is the difference between using the WYSIWYG module pointing to the CKEditor library and using the dedicated CKEditor module.
We currently use the WYSIWYG module with TinyMCE.
The answer seems to be that with the Wysiwyg module, you get an interface for which buttons appear in the profiles, whereas with just CKEditor, you don't? Or at least it's not obvious where choosing which buttons appear happens in the CKeditor module. http://drupal.ckeditor.com/ has some documentation on the subject, which says you can change the buttons.
http://drupal.org/node/606404 for some background on why CKEditor and Wysiwyg are separate efforts (though you can use CKEditor just fine with Wysiwyg).
I'd be inclined to stay with Wysiwyg so that you can swap out editors (that is, the JavaScript libraries for them) without having to swap out Drupal modules.
The CKeditor module gives you have much more granular control around where the editor windows appear, user role level permissions and the buttons available for each. The WSYIWYG API just allows for basic on/off configuration of editor windows for text fields across the whole site. Button profiles are based around input types (filtered & full HTML). The advantages of the API module is that it's not limited to just one editor (there's 10 or so) and really easy to configure.
The Ckeditor module is more difficult to configure and certainly not for most implementations, but very nice to have this module available if you require that level of control.
From my experience, using the Wysiwyg module was a better decision.
In some special cases (mainly when the editing was inside of an Ajaxed page), using ckeditor was a bad chioce.
When using the Wysiwyg, replacing the editor itself wasn't a hard task, which solved several problems very fast.
Therefore, for future situations you might not even think of now - use the Wysiwyg module.
Using the WYSIWYG module will allow you to fairly easily switch to another editor if you find one you prefer (or if new ones come onto the market).
RE: WYSIWYG module using CKEditor library vs CKEditor module
I found the former only allowed the following toolbar;
(source: johnathanthwaites.info)
Later had much more like font colour, flash embed, spell check etc.
(source: johnathanthwaites.info)
Have done a full explanation here;
Link to CKeditor
I've been using wordpress and really don't like the wysiwyg editor. I really don't want to spend a lot of time with the HTML too. What I would like is to be able to use Wiki Markup for my post. Searching for wiki markup plugins on wordpress isn't very helpful. The one plugin that looked interesting was WP-MediaWiki, but this plugin doesn't play very well with other plugins. I would really like to have Atlassian Confluence like wiki syntax.
try WP MarkItUp, it even provides creating custom markup:
"WP MarkItUp! is the WordPress plugin that replaces the old "quicktags"
toolbar with MarkItUp!, a lightweight
jQuery plugin that allows to turn any
textarea into an highly customizable
markup editor. XHTML, Textile, Wiki,
Markdown and BBcode toolbars are
already provided out-of-the-box, but
even your own markup syntax can be
easily implemented with this system.
The plugin currently features three
different skins for the toolbar, new
ones are about to come."
Currently using CKEditor + IMCE.
http://drupal.org/project/ckeditor + http://ckeditor.com/
http://drupal.org/project/imce
Are there better alternatives for a Drupal rich-text editor with image upload support?
To set it up, I add the modules, enable them, add the CKEditor source, configure the Default CKEditor profile to not load unless I tell it to, disable security filters until it loads, and enable the Drupal - Full toolbar version. This gives me all the CKEditor features and flexibility, image and flash upload support via IMCE.
I have tried CKFinder, but I rarely use it on client projects (non-free usage licences). Other modules are a pain to configure and may sometimes break the interface or content (especially around full HTML or PHP inputs).
Update 1: Added a small bounty, looking for more answers.
After having trouble with the CKEditor module over and over again, I switched to http://www.drupal.org/project/wysiwyg , which encapsulates the JS of multiple WYSIWYG Editors in a generic way (by using input filters, which somehow feels like The Right Thing to me).
Add http://www.drupal.org/project/imce_wysiwyg - the WYSIWYG IMCE bridge module, and it works almost exactly as CKEditor.module and IMCE would. A plus: It works with other editors, too, just download and install the editor JS code per the instructions.
I suggest you http://drupal.org/project/whizzywig it is light, full featured and natively includes an image browser (have a look at the comparison table).
I did a comparison on our blog a while ago, looking at some solutions.
Currently I'm sticking with wyswiwyg + imce + tinymce + imce_wysiwyg.
BUT I don't think it's the perfect solution. However in Drupal 6, we don't really have a central image library, this will be a lot better in Drupal 7.
I would recommend checking this module out:
http://drupal.org/project/nrembrowser
It integrates with CKEeditor and might be the way to go.
I know this has been asked before, but I am hoping that there are more options available now.
I am looking for a nice simple image editing plugin that I can include in my document imaging system.
It doesn't need serious photoshop type functionality, just the basics like zooming,cropping,resizing,flipping and rotating.
Doesn't have to be a freebie component, but I would prefer there to not be runtime licenses because there will e multiple implementations of our product.
btw - website is in ASP.Net
Thanks
Craig
We use CuteEditor from www.cutesoft.net, its a great html editor and has a good uploading and image editing, I think these can be used outside the editor: see: http://cutesoft.net/forums/9329/ShowPost.aspx