Posted by Sifro on July 11, 2010 at 10:40am
Hello, i'm using Drupal 6 with openWYSIWYG 1.4 and WYSIWYG 2.
Here's what i did:
1) download and install WYSIWYG
2) download and put OpenWYSIWYG in the right folder
3) enable OpenWYSIWYG for the HTMLeditor input format
Now, if i go to node/add and select the HTMLeditor input format, a "Disable rich text" link appears, but clicking on it is useless, and no editor appears. I tried to add a button, still no results.
Any help for debugging this problem?
Thanks a lot! =)
Comments
I've never heard of people
I've never heard of people using OpenWYSIWYG. I use TinyMCE for my projects and find it very good. I know of many others who prefer CKEditor or FCKEditor. I recommend trying one of those three.
Thomas Hansen
www.ThomasHansen.me
indeed it solved the
indeed it solved the problem...
i liked openWYSIWYG because it had a really nice built-in file manager (that means, no need to configure anything! :D), but it looks like that i'll have to put my laziness apart and start working on implementing a file manager for ckeditor
For WYSIWYG file editors most
For WYSIWYG file editors most people use IMCE and IMCE WYSIWYG Bridge.
http://drupal.org/project/imce_wysiwyg
http://drupal.org/project/imce
Thomas Hansen
www.ThomasHansen.me
I'm going a bit out of topic
I'm going a bit out of topic but....
any ideas why the generated HTML for chars like "à" is not the corresponding escape sequence (like & agrave;) but straight char itself?
Happens with CKEditor and TinyMCE
You could fix this with a
You could fix this with a Drupal input filter on your input format. One of the core input filters may do what you want or you can find a contributed module that provides the filter you need. Or of course, you can write a module yourself that accomplishes that task.
Thomas Hansen
www.ThomasHansen.me
Purpose
This happens on purpose and is enforced by Wysiwyg module. Reason being that, on multilingual Drupal sites, many posts may almost completely consist of non-latin characters. If the editor would convert the content to use HTML entities, such postings would almost completely be HTML entities.
Drupal's input and output is UTF-8/Unicode. Thus, we don't need to translate or convert any characters.
Daniel F. Kudwien
netzstrategen
that's interesting... even
that's interesting... even though I don't have any non latin chars, as all my texts are in italian.
Anyway, there are definetely no problems at all in using these chars without escaping? Problems with different systems with different charsets, or whatever...
Thanks a lot!
...
Yes, that's why all of Drupal uses the UTF-8 character set.
Daniel F. Kudwien
netzstrategen
thanks for all your helpful
thanks for all your helpful advices!
But there MUST be a way to fix directly it in the editor, because the standalone version works great.
For example, go to: http://giochigratis-online.net/sites/all/libraries/ckeditor/_samples/ful...
Enter a few accented letters... then, press the SOURCE CODE button, and you'll see the escaped letter. It doesn't happen inside drupal