TinyMCEComments
Why the need of a preview box if you have the What You See Is What You Get Editor in the same place as your visitors type in the comments?
This plugin turns the comment field from a primitive <textfield> into a WYSIWYG editor, using the internal TinyMCE library bundled with WordPress 2.0 or up, without the need of another separate installation. Functions that only available to writers like adding images were removed and will not show up in the toolbar.
Consider a donation :).
Current Version
0.4.3-2 - Download
Version History
0.4.3 - Support for WordPress 2.5. (gzip/cache for the script will be in 0.4.4)
0.4.2 - Support for K2 and other themes that uses AJAX Comment field, finally! (JQuery is time wasting, and it just doesn’t work for me) (And given that they are using onsubmit() to submit comments, not onclick() of the submit button!)
0.4.1 - Store comments in UTF-8 instead of HTML entities; Load TinyMCE only when there’s a comment form (Thanks José!)
0.4.0 - User supplied custom CSS; Modify interface a bit. Plugins of TinyMCE are now auto detected and can be added by clicking on the hyperlinks.
0.3.5 - Allow to change interface language; Subscript/superscript options; Allow user to add own plugins and buttons to the editor
0.3.0 - Increase loading speed; Fix IE7 disappearance of linebreaks
0.2.5 - Enable Firefox spell checking in the editor
0.2.0 - Newlines are correctly displayed and added a JavaScript function help adding text into TinyMCE editor
0.1.5 - RTL Text Support and allow to view HTML source
0.1.0 - Initial release
Instructions
The usual steps for installing and running a WordPress plugin:
- Download.
- Rename the extension from phps to php.
- Upload.
- Activate.
Known Issues
- Unwanted carriage return/newline/enter key were put into comment in older versions of Firefox. (Unconfirmed)
- Content inserted not within tags (for instance, WP Grins) are not removable by backspace. (Workaround: encapsulate in <span> tags, see updated instructions for WP Grins below)
- Message disappeared in submission using IE 6. (Unconfirmed)
- Compatibility with various comment-related plugins and customized themes. Please make sure the comment field is named “comment” and there are no other scripts that will interfere with it.
Working with WP Grins
Open wp-grins.php from the WordPress admin interface. Find
myField = $('comment');
Replace with
myField = document.getElementById('comment');
insertHTML('<span>'+tag+'</span>');
return;
Making TinyMCEComments works with other plugins
TinyMCEComments provides a JavaScript function insertHTML(text) which could be used by other plugins on the same page. It is used for inserting customized content generated by other plugins into the TinyMCE editor.
Compatibility with Akismet
Since there are some users receive complaints that the plugin increase the number of false positives of Akismet anti-spam, I sent a support request to Automattic recently. Here’s the conversation.
mk dot is dot here at gmail dot com wrote:
> Hello,
>
> I am the author of the plugin - TinymceComments for WordPress. My plugin
> just turns the comment area of the blog into a WYSIWYG editor, just like
> the one in the write page of the admin interface. Some users complains
> that if my plugin is turned on, many normal and healthy comments (without
> using special tags I suppose) were considered as spam by Akismet. I’m no
> anti-spam expert, so the only thing I can do is to ask for an advice. My
> plugin doesn’t have any server-side elements (except the admin interface)
> but purely rely on JavaScript. Mya you provide ideas so I could further
> investigate and solve the problem? Thanks in advance and I am looking
> forward to your reply.
>
> Yours,
> Thomas AuHi,
If this were all users then I think there would be a clear relationship somewhere.
As it is only some, and as it could therefore be any factor in their comment which causes this I don’t see that Akismet and your plugin are causing problems.–
Mark
Though they claimed there are no clear relationships, I’ll continue test on this. And, if your blog is okay with both plugins activated, leave me a message :).
Update: Seems I’m getting less comments eaten by the Akismet filter on my test blog (Here I use SK2). Either it could be Akismet getting used to it, or some other unknown factors acting behind the scene. Tell me your case if it’s different.
P.S.: This plugin is NOT designed to work with Live Comment Preview. Stop complaining about it.
P.P.S.: Please stop using this page as your testing ground, as the intention of the thread is for support request only. Set up a WordPress yourself, install the plugin, and enjoy yourself there. If you wish to report a bug or provide insightful and valuable comments, file your request here or e-mail me directly.
on Saturday, May 26, 2007 at 2:22 am Bob! wrote:
Excellent feature, thanks for this. Testing it on my photoblog and will see if it gets any use
on Saturday, May 26, 2007 at 2:52 am Martin Hipfinger wrote:
thanks for this plugin, but sadly i cannot use it because then "WP Grins" (http://alexking.org/projects/wordpress) doesn't work anymore. but if you would be able to fix that…
on Saturday, May 26, 2007 at 5:46 am :sviatoi: wrote:
Thank you very mutch for this plugin, it's work greatly))
on Saturday, May 26, 2007 at 4:11 pm mk wrote:
Martin:
Unfortunately I can't think of a simple way to make this work with WP Grins. I need some time to study into it. Give me some time and wait for the release of version 0.2
on Saturday, May 26, 2007 at 4:17 pm mk wrote:
Gene:
Probably the plugin you mentioned is designed to work with a <textarea> but not a TinyMCE editor. Could you give me the link to the plugin's site so I could look onto the issue myself?
And, about the space after the period. It behaves normally on the secod comment by you. Interesting. I'll look onto this further. Thanks.
on Saturday, May 26, 2007 at 4:29 pm mk wrote:
Gene:
You could always reach me via mk dot is dot here at gmail dot com. Thanks!
on Saturday, May 26, 2007 at 10:08 pm Kawamao wrote:
Nice plugin, I like it very much. But I have use the plugin <a href="http://meidell.dk/archives/2004/09/04/nested-comments/">Brian's Nested Comments<a/> too, and can't work together.Would you tell me how to use it work together?….thx..:)
on Sunday, May 27, 2007 at 12:33 am Shahzad khan wrote:
Good job mate !
on Monday, May 28, 2007 at 6:06 pm Lior Haner wrote:
I love the plugin, it works perfectly!I do have one problem, my blog is left to right (in Hebrew) and I would like the comments text to be left to right as well. I couldn't find where I can tweek that myself, any help will be greatly appreciated. Thanks in advance.
on Wednesday, May 30, 2007 at 8:17 am au8ust wrote:
Love it! Hope to see this plugin works with WP-Grin and Yahoo/MSN Style Smileys
Cheer!
on Wednesday, May 30, 2007 at 6:01 pm hartlijn wrote:
it does look very nice! unfortunenately it does'tn work with my Anarchy Media Player-plugin.
on Thursday, May 31, 2007 at 3:43 am Shawn Honnick wrote:
Good idea but does (or can) this create security issues?
on Thursday, May 31, 2007 at 11:22 am mk wrote:
Shawn:
Probably not, because the comment content will finally be filtered out by WordPress itself. Actually this is purely JavaScript.
on Thursday, May 31, 2007 at 12:55 pm David Anaxagoras wrote:
I love this plugin — a very smart, simple and elegant solution.
One question — I've noticed that suddenly long-time commenters are now ending up in Akismet's spam filter. Could this possibly have anything to do with TinyMCEComments? Or did Akismet just hiccup?
on Thursday, May 31, 2007 at 2:54 pm regisseur wrote:
Hi,
It's seems that it's not working with Wordpress 2.2
on Thursday, May 31, 2007 at 4:37 pm mk wrote:
David:
Akismet doesn't use any JavaScript technique to determine if a comment is spam.. So it is unlikely the comments are affected by TinyMCEComments itself. Though your visitors may have a higher tendancy to add links in your comment
on Thursday, May 31, 2007 at 4:38 pm mk wrote:
regosseur:
Umm.. The WordPress 2.2 installed on my machine works perfectly with the plugin. Maybe it is your theme or other plugins you've installed?
on Monday, June 4, 2007 at 7:54 pm Mike wrote:
thanks for this plugin, is working great! Also with wp-grins
(WP 2.2)
one thing is would like to know, how kan i add options in the java part of the .php file to add the options to link to an image (the part you removed
) i would like to have this function in my comments…
tia
on Tuesday, June 5, 2007 at 9:56 am buck wrote:
Great plugin!
Is it possible to add more buttons to the toolbar? I’d like to add quotes, images, ul, ol…
would it be possible to add the toolbar to contact-form plugin and to bbpress post-forms?
on Tuesday, June 5, 2007 at 11:02 am mk wrote:
Mike,
Though you could add an image button to the interface, but ultimately the image will be filtered out by WordPress itself because it may cause a security threat. (Think of anonymous users planting web bugs into your blog). You could do it by modifying the WordPress code itself, but I don't suggest to do it.
on Tuesday, June 5, 2007 at 11:04 am mk wrote:
Buck,
It's possible to add buttons, but for the effects to appear in the final result the tags have to pass the sanity test given by WordPress. You may also ask other plugin developers to implement the support of this plugin. I have provide a simple API for that purpose.
on Tuesday, June 5, 2007 at 9:03 pm Buck wrote:
Ok, thanks for your answer mk.
on Wednesday, June 6, 2007 at 12:03 am Scott Tribe wrote:
I like the plugin, but some of my readers who try to comment are finding 2 things:
1) Some of them are getting carriage returns in paragraphs where they never have hit the "enter" button in the first place (which in my Wodpress admin editor, is showing up as the html < / b r > (no spaces of course, I'm just typing it out with spaces so it shows up to you)
2) Others are telling me they are getting NO carriage returns when they hit enter - thus their comment looks like 1 big blob of text, and it can be quite unreadable.
on Wednesday, June 6, 2007 at 12:25 am mk wrote:
Hello Scott,
I'm not sure if this is a bug from the WordPress TinyMCE Editor, by me, or by some other factors unknown. Do you really see </br> showing up in your admin interface and make sure it's not <br />? (Yes, you can type the tags here without spaces)
And, could you provide more information, like the version of your WordPress installation, the browsers your readers are using (the larger the sample the better), as these information could help locate the source of the problem. Also could you give me permalinks that points to the problematic comments? Thanks a lot.
on Wednesday, June 6, 2007 at 12:39 am Scott Tribe wrote:
mk:
I just posted an open thread at my site to do just that and leave some comments - and to leave their browser and what version it is. Those have just started. (http://scottdiatribe.gluemeat.com/2007/06/05/open-comment-thread-test-postings/)
As for my version of Wordpress, it's 2.2… and as for the first part of your post, you're right.. it's <br /> I'm seeing. Here's an example of one comment with that problem which is showing </ br>'s at the end of every line.. or at least, what it reveals to me when I do an "edit comment" from Wordpress:
http://scottdiatribe.gluemeat.com/2007/06/03/what-a-shocker-not-were-parroting-the-us-on-climate-change-at-the-g8/#comment-4696
on Wednesday, June 6, 2007 at 1:03 am Scott Tribe wrote:
er.. I meant <br /> there of course, not </br>
Anyhow, mk.. just as a followup to my last post.. it appears from the initial posts in the test thread and some of the prior blog comments in other threads and looking at my stats on my end (using FIrestats to see), that for the big globs of text that are being entered without carriage returns apparently being acknowledged, the persons are using IE - IE 7 in one case in the test thread mentioned prior, and apparently IE 6.0 in this comment.. which is here:
No postings yet from people getting the inserted <br />'s yet.. I'll let you know when we get those.
on Wednesday, June 6, 2007 at 1:09 am mk wrote:
Scott,
Thanks for your help and cooperation. I'll look into it and see if there's anything I can do.
on Wednesday, June 6, 2007 at 1:22 am Scott Tribe wrote:
mk: no problem.. thanks for looking into it.
By the way, I've found from the one person who was getting <br />'s in his text when he hadn't even entered a "Enter" that he was using an older version of Firefox - 1.0.7
on Wednesday, June 6, 2007 at 4:02 am Mike wrote:
mk, thanks for the fast reply about the image stuff in the comments….
now i got an other issue (not the one which Scott describes, yet anyway) with WP2.2 & WP-Grins & Firefox 1.5 & 2 (IE works fine). When inserting a smiley, i can't delete it with the backspace button. I have to press the backspace button, then the 'undo' comes on, and then the 'undo' removes the smiley… hope you understand what i am trying to describe…
on Wednesday, June 6, 2007 at 6:23 am Ronald Huereca wrote:
I have a suggestion for your plugin page as far as search engine purposes go. Break out the keywords (Tiny MCE Comments). I searched for this plugin for over ten minutes and finally only found it after searching through the archives of WLTC.
on Wednesday, June 6, 2007 at 7:01 am Scott Tribe wrote:
mk: no problem.. thanks for looking into it. By the way, I've found from the one person who was getting <br />'s in his text when he hadn't even entered a "Enter" that he was using an older version of Firefox - 1.0.7
on Thursday, June 7, 2007 at 1:34 am mk wrote:
Ronald,
I think making a unique keyword for this plugin is better than breaking into multiple existing keywords, or this page will be behind many existing pages with "TinyMCE" and "comments", which are both very common keywords.
on Thursday, June 7, 2007 at 1:38 am mk wrote:
Scott,
I think I've fixed the IE7 line break disapperance problem, but need a bit more testing to make sure I did it. For the one who get unexpected <br />'s, since I don't have 1.0.7 at hand, I will put the work in lower priority and will fix the WP Grins compatibility first.
on Thursday, June 7, 2007 at 4:45 am Tomsn wrote:
How can i add the Tinymcebar in a non-standard Theme? only Pluginaktivate have no effect…
on Thursday, June 7, 2007 at 5:15 am Tomsn wrote:
Next Problem on other site: when i add Tinymce-comments AND live-preview-comments, the tinymce-comments work but the live-preview did stop working, after disable tinymce, the live-preview works as well …
(hope u unsderstand this …)
i have WP2.2 with Notsofresh Theme
and WP2.1.3 with gluedideas_subtle Theme
on Thursday, June 7, 2007 at 9:44 am mk wrote:
Tomsn,
Hello, if Tinymcebar means TinyMCEComments, most probably the theme is not using "comment" as the comment box name, but it is quite rare and maybe need a lot of modifications. I'll follow it after I've completed the fixed at hand.
And, TinyMCEComments is not designed to work with live-preview comment plugin. My idea is if you already can view the result in the editor, why do you need another place to display the result?
on Friday, June 8, 2007 at 4:14 am greg wrote:
I also love the plugin, thanks so much.
I noticed the same thing that a commenter above noticed… suddenly long-time comments are ending up caught by Akismet. It's not all my commenters, but it does seem strange that this problem started after installing this plugin.
Thanks again!
on Friday, June 8, 2007 at 4:28 am Martin Daugaard Stevnhoved wrote:
Hi … thanks for a nice plugin.
I have a suggestion to a tiny improvement.
On the option-page you could have a listbox showing the names on the js-files found in /wp-includes/js/tinymce/langs/ so the admin could select a language-pack for TinyMCE.
The only thing that should be added to the comment-code is a "language : <filename without .js>" option to the tinymce javascript.
on Friday, June 8, 2007 at 5:51 pm Mike wrote:
mk, i have another issue with tMCEc (v0.25 & 0.30)
when posting a rather large message with IE, it is not being posted. The message will not appear and is not held bij wordpress. Don't have this problem with firefox 1.5 &2
on Friday, June 8, 2007 at 11:15 pm mk wrote:
Mike,
What version of IE you are using? I have no problem using IE 7.
on Friday, June 8, 2007 at 11:16 pm mk wrote:
Greg,
I think I'll check the issue with the Akismet author. Thanks for notifying.
on Friday, June 8, 2007 at 11:17 pm mk wrote:
Martin,
I'll add more features to tune the TinyMCE in later versions. Stay tuned
on Saturday, June 9, 2007 at 1:59 am Mike wrote:
mk, i can reproduce the problem with IE 6.0 (at my home and all my IE 6 users report the problem) don't have IE7, so can't test it…
on Saturday, June 9, 2007 at 5:13 am Patrice wrote:
really great plug-in!!!
on Saturday, June 9, 2007 at 10:59 am David Anaxagoras wrote:
I disabled this plugin for a short while to see if I still had Akismet issues. Without the plugin — no false positives. With the plugin — many false positives. Shame, it was a good idea, but it must remain disabled for now. My commenters were NOT including links in their comments.
on Saturday, June 9, 2007 at 12:48 pm mk wrote:
Hello guys,
I've just wrote a support request to Akismet Blog. Now we have to see if they could provide solution/explanation for this. Thanks all for your support :).
on Wednesday, June 13, 2007 at 1:51 am Laura wrote:
Nice plugin but I am having one problem with it. Everything looks fine on the blog but when the comments are mailed to me quotation marks appear as " and apostrophes appear as '. Any ideas why this is happening?
on Wednesday, June 13, 2007 at 5:27 pm mk wrote:
Laura,
Have you installed any plugins that also "interferes" the comments?
on Thursday, June 14, 2007 at 4:47 am Greg wrote:
@mk - thanks for trying to dog it down, I hope you can figure out what the issue is, I really do like this plugin. I just posted something else that got some comments, one made it through Akismet, one didn't, and I can't see any difference in the content of the comments (no links, etc.).
on Friday, June 15, 2007 at 9:34 pm Scott Tribe wrote:
HI Thomas:
I saw this new plugin from yesterday that is related to yours, and thought you might be interested in looking at what he does and perhaps looking to implement it for the users in a future update for your plugin.
on Saturday, June 16, 2007 at 5:51 am Ploupi wrote:
What a great plugin !!!
Unfortnately, it doesn't work with the plugin "AJAX Comments"
Can you resolve that ?
Thanks
on Sunday, June 17, 2007 at 4:03 pm mk wrote:
Ploupl,
Unfortunately AJAX Comments is not designed to work with plugins that do visual modifications on the comment field (due to scriptaculous effects). And you have to modify it manually, but I can't come up with any guides at the moment. Sorry.
on Monday, June 18, 2007 at 2:08 am mk wrote:
Scott,
Thanks for your suggesting, I've put your idea into the new version, but instead of modifying the PHP source code, I try to make it a little bit more user-friendly by putting that into the admin interface. Hope you like it :).
on Wednesday, June 20, 2007 at 4:51 am Ploupi wrote:
Thanks for the answer.
But with my new theme glossyblue, it works (i have uninstalled tinyMCEComments and reinstall it AFTER installing Ajax Comments )
But now, it seems it doesnt work with The theme switcher : only my theme by default works, the others haven't toolbars and smilies are useless
on Wednesday, June 20, 2007 at 8:50 am Laura wrote:
This is the only one that causes this problem. I do have two other plugins that work with the comments. Both were installed before this one and were working fine.
on Thursday, June 21, 2007 at 12:25 pm mk wrote:
Ploupi,
Maybe the theme you are using does not has the default name for the textarea, i.e. "comment"?
on Thursday, June 21, 2007 at 12:25 pm mk wrote:
Laura,
Would you mind telling me what plugin you installed with your blog? Thanks.
on Thursday, June 21, 2007 at 9:58 pm greg wrote:
mk - any word on the plugin conflict with Akismet? I've had to disable yours for the time being, but I'm really excited to use it… Thanks!!!!
on Friday, June 22, 2007 at 11:35 pm mk wrote:
Greg,
No… Even if there exists a problem, this is one I could not control. The message different from plain comment and sending from this plugin, maybe is just a few more HTML tags the visitor uses.
on Sunday, June 24, 2007 at 2:34 am Martin Daugaard Stevnhoved wrote:
Hi.
I just discovered that you added the language-option to the plugin. Nice.
An other feature that could be really nice, were if you could select your own style sheet, so the comment field could be styles as the theme. Maybe the plugin could look for a specific file (eg. comments.css) in the active theme-folder, and use it for the content_css parameter. If the file doesn't exist, of course it could use the default wordpress.css file.
Just an idea.
on Sunday, June 24, 2007 at 2:19 pm mk wrote:
Martin,
Thanks for your comment.
I'll incorporate the function to the next release.
Cheers
on Wednesday, July 4, 2007 at 12:47 am Kjetil Flekkoy wrote:
Hi
I've had a problem for some time: It's impossible to add comments to my blog. After some back and forth (activating and deactivating plugins) it seems that probably your Tiny plugin is not compatible with the K2 theme.
Tried to upgrade to latest Tiny version, but no luck. Even the formatting buttons above the comment field didn't show up - so my guess is that Tiny/ K2 works badly together.
Just liked to let you know
Kjetil
Running WP 2.2 and K2 0.95 with these plugins active:
- Akismet 2.0
- Disable WordPress Widgets 1.0
- E-mail users 2.3
- Page links to 1.4
- RS-discuss 0.5.2
- SEO title tag 2.0beta8
- Subscribe to comments 2.1
- Target Blank In Posts And Comments r1.0.1
- TinyMCEComments 0.1
- Ultimate Tag Warrior 3.14159265
- WordPress.com Stats 1.0
- WordPress Database Backup 2.1.2
- WP-EMail 2.10
- WP-SlimStat 0.9.2
on Wednesday, July 4, 2007 at 7:42 pm mk wrote:
Kjetil,
Thanks for notifying. I'll try to make it compatible with K2 in the next version of the plugin.
on Saturday, July 7, 2007 at 8:59 am Sproke :0) wrote:
Hey there, just letting you know that I’m having trouble implementing this plugin with Brians Threaded Comments http://meidell.dk/archives/2004/09/04/nested-comments/ It works fine if I don’t want to reply to a particular comment, but if I reply to one in a thread, it looks fine, but I cannot type in the comment box. I have also pasted this bug on Brian’s threaded comments page. I would love to be able to use these two plugins in conjunction! Please help! And Thanks in advance
Sproke :0)
on Thursday, July 12, 2007 at 5:22 pm Lucas wrote:
Hi there!,
Just wanted to inform you that this plugin does not seem to work with Firefox 2.x.
Also in IE this plugin breaks the WP-Grins plugin. If I apply the fix above (working with wp-grins) grins start to work with IE but stop working with Firefox.
Will drop by once in a whil ehoping for a fix
Cheers,
Lucas
on Thursday, July 12, 2007 at 8:24 pm mk wrote:
Sproke,
Please read the Making TinyMCEComments works with other plugins above. The modification is easy and should help.
on Thursday, July 12, 2007 at 8:27 pm mk wrote:
Lucas,
What version of Firefox are you using exactly? My Firefox 2.0.0.4 on Windows is working perfectly with the plugin.
And for the WP-Grins fix… I'm not sure if <span> really work wells. Maybe you could replace that with other tags with no effects on the layout (How about a css-ed <div>?).
on Friday, July 13, 2007 at 4:44 pm Lucas wrote:
Hi MK,
I am also using version 2.0.0.4.
Did you also try it on my website? Would be strange if it is working for you
About the fix, if I apply it I am no longer able to add smilies using firefox (so it does not affect the layout). I will experiement using different tags though and let you know if I succeed to fix it.
Thanks for your support.
on Saturday, July 14, 2007 at 8:25 pm mk wrote:
Lucas,
Just checked out your web page. I discovered that one of the variable of the TinyMCE script(one called realTinyMCE) real does not load properly. Posts here suggests that some other plugins may interfere TinyMCE editor and preventing it working properly. Check it out and see if that helps
on Sunday, July 15, 2007 at 5:43 am Bobblehead wrote:
feryvery niceplugin!using it on my site as well.
greetings!
on Thursday, July 19, 2007 at 2:00 am Laurel wrote:
I met the same prob as Lucas, and finally I found it was caused by lightbox. I changed
<script type="text/javascript" src="http://…/lightbox2.03.3/js/scriptaculous.js?load=effects"></script>
to
<script type="text/javascript" src="http://…/lightbox2.03.3/js/effects.js"></script>
in the head section, then both works!
But I found another prob now, when I click the "Insert/ edit link", I got "Error: inst has no properties
Source File: http://www.guiguan.net/wp-includes/js/tinymce/tiny_mce_gzip.php?ver=20070326&theme=advanced&language=en&plugins=&lang=en&index=0
Line: 90". Even in ur site, also exist this prob~ hum, really trouble some to play with WYSIWYG in wordpress.
on Saturday, July 21, 2007 at 1:47 am José Luís wrote:
Since TinyMCE is downloaded as a PHP file (tiny_mce_gzip.php) it does not get cached…
How do I enable TinyMCEComments to use Apache caching?
on Saturday, July 21, 2007 at 10:32 pm José Luís wrote:
Hi, I found kind of a workaround: I changed line 220, associating your plugin to comment_form hook. This way, only pages with comment forms download TinyMCE…
add_action('comment_form', 'addTinyMCESupport'); // JLCarneiroon Sunday, July 22, 2007 at 7:32 pm andy wrote:
There is certainly something going on with WP marking many comments as spam. I have installed this great and simple plugin on a small, private site restricted to a small number of registered users. I am NOT using Akismet or any other third party spam tools.
Yet something like 15-20% of perfectly safe and short comments are getting marked as spam by the built in WP spam filters. The problem here is, of course, is that WP never shows these on the comments admin pages so to the novice user they appear to have just been lost. But there they are in the database all the samne with an approved marking of 'spam'.
I don't believe this is a problem with your plugin. This is quite clearly a problem with WP even if they wont consider it.
If my investigations get anywhere I'll come back here and let you know.
on Sunday, July 22, 2007 at 10:49 pm mk wrote:
José,
Thanks for your suggestion. I will move it to the source when I am free from my daytime work.
on Sunday, July 22, 2007 at 10:50 pm mk wrote:
Andy,
Thanks for your help. I am looking forward to see the result.
on Sunday, July 22, 2007 at 11:34 pm andy wrote:
OK - here is what is happening. First leaving Akismet out of the equation.
TinyMCE encodes characters (such as an apostrophie) into XML/HTML entities. So for example, an apostrophie is encoded to ampersand + hash + 39 + semi-colon before beng presented to the back end for saving.
Wordpress checks the comment for validity and as part of that checking it runs a function called wp_blacklist_check. This function explicitly looks for any string that starts ampersand+hash, is followed by a number and closes with a semi-colon. If it finds such a string in the comment text (or the author name, email or url) then it marks it as spam.
Using standard WordPress, this means the comment is saved, the approved flag is set to spam and it is never seen - not even appearing in the comments for moderation list.
My guess is that if you use Akismet, it accepts that spam flag without question but at least puts the comment in the Akismet list.
Having traced this I can see that the 22 recent comments since installing this plugin that are invisible as such all have an apostrophie. All the comments that were passed as valid did not have one.
The next task is to work out what to do about this of course…
on Sunday, July 22, 2007 at 11:55 pm mk wrote:
Alex,
I think of two ways, where 1 is modifying the wp_blacklist_check() function, but I think it's a bit hard without compromising WordPress security…
So the second option is to modify the entity list that TinyMCE is keeping, but I don't know what side-effects this mod would bring…
on Monday, July 23, 2007 at 12:06 am andy wrote:
Yes I am coming to the same conclusion. The odd thing is that the default entity-encoding for TinyMCE is suposed to be named yet for some reason on this plugin it is numeric. I have just added a specific entity-encoding named to the plugin TineMCE init and of course, it works fine. But I am unsure as to the implications of this is terms of trapping genuine spam.
Does anyone have any knowledge on this aspect?
on Monday, July 23, 2007 at 3:34 am andy wrote:
Sorry - take back that last comment. It IS running as named it's just that an apostrophie 39 does not have an entry in the entities list.
on Wednesday, July 25, 2007 at 6:18 am Mates wrote:
I tried run WP Grins and TinyMCEComments together. I had problem with posting two similar smilies. When I used standard solution I had ":lol::lol" instead of smilies. So I replaced
<code>
myField = document.getElementById('comment');
insertHTML('<span>'+tag+'</span>');
return;
</code>
by
<code>
myField = document.getElementById('comment');
insertHTML('<span> '+tag+' </span>');
return;
</code>
and in line 120
<code>
' ' +tag+ ' '
</code>
by
<code>
'<span> '+tag+' <span>'
</code>
Now everything works fine.
(WP 2.2.1, WP Grins 1.5, tinyMCEComments 0.4.0, theme TerraFirma 3.3.1)
on Wednesday, July 25, 2007 at 6:45 am Mates wrote:
I tested tinyMCEComments with my others plugin however myGallery 1.4b10 is incompatible (imposible to insert smile from WP Grins, tinyMCEComments button bar is hidden).
on Thursday, July 26, 2007 at 10:38 pm Tal Galili wrote:
Great plugin, thanks !
on Friday, July 27, 2007 at 10:36 am Jennia wrote:
image test
<img src="http://farm2.static.flickr.com/1207/558954654_6deacb8408.jpg?v=0">
Thanks!
on Friday, July 27, 2007 at 10:38 am Jennia wrote:
img test
[img]http://farm2.static.flickr.com/1207/558954654_6deacb8408.jpg?v=0[/img]
on Sunday, July 29, 2007 at 10:29 am Malaga wrote:
Hello, please make it work with wp ajax edit comments…and better work with loghtbox, since even with your tips, i cant use it(i use thumbnail preview).
Im so bored to disable 2 or more plugins every new plugin installed…
on Sunday, July 29, 2007 at 10:32 am Malaga wrote:
I have an update to write…it works with wp ajax edit comments, BUT NOT with IE7….with firefox and opera works well…there's a bug somewhere(maybe)…please check it out.
on Tuesday, August 7, 2007 at 4:56 am Alex wrote:
Excellent! My only wish, as sickeningly redundant as it might be: compatibility with Ajax comment preview - then folks would see exactly how things will appear (this editor presents different formatting from what a final page does).
But thank you. This is great.
on Saturday, August 11, 2007 at 4:27 am Ken Gagne wrote:
I agree: if it is within your ability (and not Michael Adams'), compatibility with
http://blogwaffe.com/ajax-comment-preview/
would make your plug-in a must-have! For now, though, I must choose between the two…
on Sunday, August 26, 2007 at 9:19 pm Xi wrote:
和这个插件不兼容http://www.mybrand.com.cn/news_wp/2007/07/14/16
报告完毕
on Thursday, September 6, 2007 at 3:52 pm Gombo wrote:
Very nice and helpful, thank you. Saves a lot of trouble.
on Thursday, September 13, 2007 at 9:02 am david wrote:
Great plug, is there anyway to get the embed video icon from the "embedded-video-with-link" plug in the comments, I know you took some icons out how hard would it be to put one in. also any way to make it customizable?
Thanks,
Dave
on Saturday, September 15, 2007 at 1:52 am iNULL wrote:
Hi….
First of all, thanks alot for this plugin. I used it in wordpress 2.2.2 but unfortunately its work only on Opera v9.23 and IE6/7, NOT on Firefox 2.0.0.6 on Windows. You can see <a href="http://aufklarung.org/?p=141">here</a>. TinyMCEComments is NOT only doesn't work on my blog, but on <a href="http://mk.netgenes.org/my-plugins/mcecomments/">netgenes</a> blog too. I'm viewing this site/blog using these browser above and I'm not see the TinyMCEComments in comment area, once again its only on Firefox 2.0.0.6 on Windows! So, please give solution !
Blessing,
iNULL
on Saturday, September 15, 2007 at 8:57 am mk wrote:
David,
You could load the plugin using the interface directly, but I'm not sure if WordPress itself will filter the video tag (possibly <embed>) it made.
on Saturday, September 15, 2007 at 9:13 am mk wrote:
iNull,
First of all thanks for your report. But after checking it( I mostly work on Linux), both IE 6/7 and Firefox 2.0.0.6 on Windows works well with the plugin (at least on my site). Unfortunately it doesn't work on yours. possibly conflicted with other JavaScripts? Also if you could not see anything using these browsers, consider if there are any javasscript blocking plugins like NoScript activated.
on Monday, September 17, 2007 at 5:09 pm 7 wrote:
It's a greatest plugin! Thanks!
on Monday, September 24, 2007 at 12:00 am canarkadaş wrote:
Thanks..
[…] <a href="http://worldarchivetr.com/wp/100-wordpress-eklentisi/" rel="nofollow"> Açıklamalı 232 Wordpress eklentisi (Agu. 15, 2007 !!) (Wordpress plugin list),</a>[…]
on Tuesday, October 9, 2007 at 12:39 am Karat wrote:
Hello!
Can you tell me, how can i use Brian’s Threaded Comments and TinyMCEComments? Than i use answer in a thread, comment form don’t give me write.
on Tuesday, October 9, 2007 at 12:40 am Karat wrote:
I mean, It works fine if I don’t want to reply to a particular comment, but if I reply to one in a thread, it looks fine, but I cannot type in the comment box.
on Saturday, October 13, 2007 at 4:32 am Chuck wrote:
plug in doesn’t work with Wordpress 2.3 fix the thing.
on Monday, October 15, 2007 at 1:25 am Eddi wrote:
i’ve read the Making TinyMCEComments works with other plugins above, but still can’t fix the problem. so, all wordress plugin to allows commenters to quote other comments in their reply, likes Brian’s Nested Comments, Brians Threaded Comments, Quote Comment, Quoter can’t work together with TinyMCEComments. the quote text can’t be moved in to the comment area.
on Sunday, October 28, 2007 at 6:01 pm Richard wrote:
Hi - love the plugin, but not sure how to turn on the spell checker like in the Admin write post screen on comments.
on Thursday, November 1, 2007 at 3:56 pm CypherHackz wrote:
I’m using your plugin but the css file that I set in the admin panel is not working. Can you explain to me how to use it?
on Thursday, November 8, 2007 at 9:39 am boiledbeans wrote:
Thanks for the plugin, our users love it!
But, I think TinyMCE comments plugin interferes with Wordpress’s spam recognition mechanism. Because, after installing this plugin, we faced many problems and we had to remove wordpress’s spamming mechanism completely to keep the plugin running!
I believe this is happening because this plugin maybe messing around with nonce generated by WP.
If you know how to fix this, please let us know. Otherwise, we will debug it when we have some free time and let you know.
Thanks again for a nice plugin
on Saturday, November 10, 2007 at 8:21 pm mk wrote:
boiledbeans,
I would be gratful if you could shed some light on this issue. Many encounter the glitch as well when they are using Akismet.
Thank you for your support
on Monday, November 12, 2007 at 12:56 am Jérôme wrote:
Hi,
Good plugin, but it’s incompatible with the Sociable FR plugin
If i active this plugin, i lost the box of tinymcecomment.
:os
How resolve this problem?
on Sunday, November 18, 2007 at 1:05 am theddy wrote:
Thanks very much for your great plugin.
One litte problem. My blog is running with charset utf-8. Posts made as admin with TinyMCE are stored in the database also with charset utf-8.
The comments written with TinyMCE when your plugin is running are stored in the database in HTML code. Is it possible to tell your plugin to store comments in utf-8 as well.
Thanks a lot.
Martin
on Sunday, November 18, 2007 at 1:55 am mk wrote:
theddy,
1. If you are using pure Latin language, UTF-8 encoding = ASCII. That’s nothing to do with HTML.
2. If you see HTML codes in comments, most probably your visitors are typing the code directly in the window, and TinyMCE helps replacing those into what we call HTML entities, for example < will become < .
3. If you wish your visitors to type in HTML code directly, I suggest tick the "Allow visitors to view HTML source of their comment" checkbox in the admin panel.
Hope this helps.
on Sunday, November 18, 2007 at 2:47 am theddy wrote:
@mk
I am not using "pure latin code" - the blog is in German and the charset is set to utf-8 - so there are Umlauts, eg. äöü.
If I edit a new post as admin with TinyMCE I see in the datebase that text is stored in utf-8 code.
If TinyMCE Comments is disabled and a reader edits a comment with this simple editor the comment is stored with utf-8 code in the database as well.
But if I enable TinyMCEComments the text is stored as HTML-code in the database. A German ä is stored as & u u m l ; (I used spaces that you see the code).
My question now: Is it possible that TinyMCEComments stores the edited text in the database as utf-8 as well.
Martin
on Sunday, November 18, 2007 at 8:59 pm mk wrote:
theddy,
I see, you are complaining non-latin characters turning into HTML entities.
You could add a option to the initialization parameters of TinyMCE by editing the plugin, where inside you could find tinyMCE.init, followed by brackets.
Add the following inside the brackets:
entity_encoding : "raw"
See if that works.
on Monday, November 19, 2007 at 3:49 am theddy wrote:
Yes - great! I make some more tests but I thinks it works now!
Thanks a lot.
Martin
on Thursday, November 22, 2007 at 3:52 pm LOmiG wrote:
Hi,
i would like to use this great plugin on my blog, but i don’t know how to choose the buttons i want to appear in the editor. I would like the ‘ul’ ‘ol’ ‘li’ stuff to appear, as the ‘blockquote’ stuff. Can someone help me to do that ?
thanks,
on Thursday, November 22, 2007 at 9:45 pm mk wrote:
LOmiG,
You could take a look at here, see the names for the buttons you want, and add the corresponding IDs into the button fields in TinyMCEComments panel. If the buttons are not available, probably you’ll need to create a plugin (Or get TinyMCE Advance) for that.
on Friday, November 23, 2007 at 4:01 am J.K. wrote:
Hey Gang,
An apparent conflict between TinyMCEComments and the Lightbox 2 Plugin causes TinyMCEC to fail in Firefox.
Any help to resolve would be appreciated. - Thanks!
(Firefox 2.0.0.9 / Vista 32 Bit)
on Sunday, December 2, 2007 at 10:46 pm Jérôme wrote:
Hi,
How to enlarge the text area of tiny mce comments? Mine is small, I would like to enlarge his
thx
on Monday, December 3, 2007 at 7:37 am mk wrote:
Jérôme,
Please adjust the original textarea size (cols property of the HTML tag).
on Tuesday, December 11, 2007 at 7:40 pm aeric wrote:
just wanted to see if images linking worked!
on Tuesday, December 11, 2007 at 8:08 pm mk wrote:
aeric,
No, if you have read the comments above, you’ll know it doesn’t; It was filtered out by WP by default, as it may raise security issues.
And, to all,
I will disallow comments for this page from now on. I’m annoyed by E-Mail alerts because there are so many testing posts. To report a bug, or suggest an enhancement, please use the WordPress plugin repository.