Tue 16 May 2006
Yesterday, I notified the author of EditMonkey about the pre tag bug patch, However, he already made his mind about dropping support of FCKeditor for EditMonkey 3.0. Although personally I prefer FCKeditor, I agree that focus on one editor is better for stability issues with only one developer working on it.
Due to working on SJSD, I am pretty familiar with FCKeditor code base. When I tried the built-in tinyMCE editor of WordPress, I noticed it supports <!–more–> and <!–nextpage–> much better than the FCKeditor does in EditMonkey 2.5: in tinyMCE, an image is displayed instead of an invisible comment.
I noticed this post in regarding to this issue in the EditMonkey forum:
This can’t be fixed. I spent a week trying to get visual aids to show up in FCKeditor with an FCK plugin only to discover that this can only be done by extensively hacking the innards of FCKeditor. The two images are provided just in case someone does figure out a way to do this through the plugin. Unfortunately, as detailed in other posts, do to the difficulty in working with FCKeditor, I won’t be supporting FCK in any further releases of EM.
It looks like that "someone" happens to be me: I am pretty sure a FCKeditor plugin can achieve this (talking about version 2.2 here).
If you are fans of FCKeditor, than you may want to try this EditMonkey 2.5 Patched by Cougar version. It fixed lots of bugs related to FCKeditor interface. This download file does not contain tinyEMC and dictionaries. Unzip this file under your wp-content/plugins directory is enough.
However if you need dictionaries, you can unzip the original EditMonkey 2.5 file first, then uncompress this one to overwrite FCKeditor related part.
This is a ChangeLog compared to the original EditMonkey 2.5:
- Better <!–more–> and <!–nextpage–> support: at least as good as the tinyEMC counterpart
- Complex PRE tag content is supported, and new lines are preserved correctly
- Content saved to database is ensured to work with the builtin WYSIWYG editor as well as the builtin plain editor
Hope you enjoy it.
RSS feed for comments on this post. TrackBack this post
May 16th, 2006 at 7:31 am
Nice work!
May 16th, 2006 at 8:23 am
Cougar,
seems it only works in IE? Hope you can update it to support other browsers.
May 16th, 2006 at 4:34 pm
ah? I developed it under firefox, so it definitely works under firefox.
Ah, you use windows, don’t you? It works under linux but somehow does not work under windows. I will look into it.
May 16th, 2006 at 4:58 pm
I confirmed it works fine as well in firefox under windows.
If you can not see the images, It is caused by the cache in the firefox (even after you clear your cache, it in fact is still there, this only affects windows version). You can try to reload these two files in firefox (refresh):
Then try to reload your edit interface, it should work all right.
May 17th, 2006 at 4:30 am
Thanks!
It works perfectly. I made a mistake
There are always caching problems with Firefox under Windows. Even modifying the editor area CSS will have a latency before showing up in the browser. I just tried to clean the cache directory under wp-content on PHP server, but didn’t expect it’s a browser side issue.
I prefer FCKEditor to tinyMCE (I think most people believe it), so i’ll always notice your blog:)
May 17th, 2006 at 5:27 am
Another difference:
the original version wrapped the post content in tags, but the modified version didn’t.
Due to the CSS settings, if there is not tags around the post content, my blog can’t display correctly. So now i’m still using the original editormonkey.php file. I cann’t figure out which code made the difference.
May 17th, 2006 at 5:29 am
Sorry the tags are trimmed off.
The phrase “tags” in the previous comment refers to <p></p>
May 17th, 2006 at 6:56 am
You are right, the cougar version does not replace \n\n to make a paragraph out of it
However, you can explicitly add a paragraph tag around your text by clicking the “normal” item under Format combobox (You only need to do this for first/second paragraphs, and following enter keys will generate a new paragraph automatically)
Yes, this is very annoying and it should be better tackled by a full DOM precessor in the server side. As I am also the author of SJSD (which contains a full PHP dom processor for an advanced CMS), I will make the code standalone and incorporate it in EditMonkey.
May 17th, 2006 at 10:01 am
Thanks.
Now there’s another problem. If the content contains images, it can’t display source. When clicking the “source” button, the dialog shows up, but the source content is always “Loading. Please wait…”. If there is no images, everything is OK.
Now if I want to edit source, first I must delete all images in the post
May 17th, 2006 at 4:10 pm
oops, this is definitely a bug
fixed, please re-download the file. (Two lines in a javascript file was commented out accidently)
May 18th, 2006 at 3:38 am
Still there is a problem(how annoying am I
).
‘\n’ is not replaced by <br/> tag.
When I paste a piece of code, it becomes a mess.
Would you fix it, or is it a design purpose?
Thanks.
May 18th, 2006 at 3:46 am
What you discussed are very benefit for me to solve the problem,
Surprisingly, I find that Zhou is my classmate.
May 18th, 2006 at 3:51 am
To zhou:
please wrap code in a pre tag (select formatted in the format dropdown menu)
\n has no meaning in XHTML
Yes, you are very demanding
To kenwell:
Hehe, the world is so small
May 19th, 2006 at 11:46 pm
DONT WORK At all here!
on IE, NO and more boring the Image function menu does not work !
So i go back to original Monkey
May 20th, 2006 at 12:07 am
Without any details, I can not investigate the issue. However others can confirm this version is working better than the FCKeditor shipped with the original EditMonkey.
May 22nd, 2006 at 11:56 am
Hi Cougar! i’m the author of the previous post!
And i take the time to come bask to say : ALLELUYAH;: it works!:!:
It was the server that cache the php..
So today all works PERFECTLY ))
BlessU man ! FCK is far the best editor for Wordpres!! so thanx for your work!
And come to see 9/11 vidéos: http://ReOpen911.info
May 31st, 2006 at 11:29 pm
I’ve modified your version of the WordPress plugin for FCK to include graphics for the more and nextpage tags.
FCKMonkey is based of EditorMonkey 3.0beta. Unlike EM, it’s a very streamlined plugin, more akin to ChenPress, and leaves the configuration to the user.
BTW, I still can’t access the SF repository, and this captcha is really difficult to read.
May 31st, 2006 at 11:47 pm
I think in my patched version, “include graphics for the more and nextpage tags” was already implemented. May I know what’s new in your new release?
I have no clue what ChenPress is…
If you can tell me what’s the error when you access the SF repository, I may give a hand to solve it.
Oops, I meant to disable the Captcha! plugin, but somehow reactivated it by accident, fixed now
December 6th, 2006 at 12:46 pm
Awesome! Thanks so much! You really cleaned up the functions well!