Ajax Edit Comments 2.0 Released

Home » WordPress » Blog article: Ajax Edit Comments 2.0 Released

By Ronald Huereca on May 24, 2008.

After several betas and release candidates, Ajax Edit Comments 2.0 (for WP 2.5) has officially been released.

For plugin information and features, please visit the Ajax Edit Comments 2.0 page.

For videos and screenshots, please visit the links below:

If you run into any issues, please read the FAQ or visit the support page.

You may also leave some test comments below, but please be aware that test comments will periodically be removed.

Random Posts

50 Comments

Yeah, that’s great. Thanks for this plugin.

Comment by Markus — May 25, 2008 @ 12:16 am
You’re welcome Markus. Hope this was a good upgrade for you.

Comment by Ronald Huereca — May 25, 2008 @ 3:15 am
OK. It looks efficient.
I allow a lot of comments on my website so it is very useful.

Comment by Jerry Fobik — May 25, 2008 @ 9:20 am
This is a great plugin — I love the new look and editing screen. However — there are issues with this release. Everytime someone edits a comment, it’s injecting code into the RSS feed which shows up as posts. I updated last night and then again this morning, but the problem persists. I’ve disabled the plugin until this gets sorted.

nina aoki

Comment by nina — May 25, 2008 @ 11:50 am
@nina,

Thanks for the feedback. I updated the 2.0 version and changed the way the security keys were being posted. Instead of using the built in WP function, I now insert them directly in. Perhaps that’s what was causing the RSS issues.

If you could re-download the plugin and perhaps get back to me, that would be great. If you’re still having issues, please send me the errors you are receiving as I wasn’t able to duplicate the extra code being inserted.

I’m thinking it’s either the way I was storing security keys, or it’s a plugin conflict, so seeing the erroneous code would be helpful in tracking down the issue.

Comment by Ronald Huereca — May 25, 2008 @ 2:53 pm
@Ronald

Yes — that’s what’s showing up in the RSS feed. A title “Ajax Edit Comments Security Key” and a long string of characters. When I cleared the keys in Settings and re-sync’d my feed, they disappeared, but as soon as someone edited a comment again, they were reinserted into the RSS feed.

I will wipe the plugin and reinstall and see if the problem persists.

Thanks,

nina

Edit: to test non-admin editing

Comment by nina — May 25, 2008 @ 4:33 pm
I just noticed 404 errors in my logs like this:

http://www.untwistedvortex.com/2007/02/24/wp-includes/js/thickbox/loadingAnimation.gif

I checked the page source and saw this:

![CDATA[ */
wpAjax = {
noPerm: "You do not have permission to do that.",
broken: "An unidentified error has occurred."
}
/* ]]> */

It looks like a permalinks issue.

Comment by RT Cunningham — May 26, 2008 @ 1:05 am
The odd part is that everything works as it should, logged in or not logged in. I can do a regex redirect to get rid of the 404 error, but I have not idea what the error in the source is generated by.

Comment by RT Cunningham — May 26, 2008 @ 1:12 am
I just checked the first commenter’s blog and it has the same permalink structure as mine and shows the same things. I don’t know a blog that doesn’t have dates or I’d check one to see what script is misbehaving. Wait…this blog… checking…

Comment by RT Cunningham — May 26, 2008 @ 1:58 am
Okay, this blog shows the source with the same thing as mine.

Comment by RT Cunningham — May 26, 2008 @ 2:00 am
@RT,

The loading animation is used by the thickbox script. The loading animation is a relative link, and the first thing I do in my plugin is fix the URL. Not sure what’s causing it to load though, as it shouldn’t load until someone clicks the edit button.

Comment by Ronald — May 26, 2008 @ 12:28 pm
Hi Ron, thank you thank you for this lovely plugin! I seriously would not be without it.
But (you knew there was a “but” coming, right?) I just tried the “upgrade automatically” thing through WP and it said it was unable to remove the old plugin. I don’t know if that’s an issue with our server or your plugin, but I thought you might want to know.

…editing my own comment just because I can…

Comment by Sue @ TameBay — May 26, 2008 @ 1:05 pm
Just found out that the release I put out yesterday (for Nina, still 2.0) fixes another bug where security keys were showing up in search results.

The latest 2.0 download will fix this as well. If any of you have these issues, please re-download 2.0 and clear your security keys. It should be the last option in the Ajax Edit Comments admin panels.

I’m sorry I couldn’t find this error before the official release.

Matt Mullenweg himself told me this is a good way to store plugin data, but I’m beginning to think different.

Comment by Ronald Huereca — May 26, 2008 @ 5:47 pm
@ Ronald

Okay thanks — I’ll redownload and try that.

Thanks much!

- nina aoki

Comment by nina — May 26, 2008 @ 6:07 pm
Hey Ronald – thanks for this plug-in. Very useful.

I’m having the same issue that RT mentions above. I have scripts running that email me whenever a 404 happens and it won’t stop with this wp-includes stuff. I know you’re linking to the thickbox javascript images. But there’s something about the way it’s constructing the URL. In your code you have:

imgLoader.src = “<?php bloginfo(‘wpurl’) ?>/wp-includes/js/thickbox/loadingAnimation.gif”;
tb_closeImage = “<?php bloginfo(‘wpurl’) ?>/wp-includes/js/thickbox/tb-close.png”;

…which should work, but the URL’s that actually get generated seem to be relative to the post…

/2008/05/26/wp-includes/js/thickbox/loadingAnimation.gif
/2008/05/26/wp-includes/js/thickbox/tb-close.png

Comment by Suzanne — May 27, 2008 @ 12:14 am
It looks like bloginfo(‘wpurl’) is the culprit that’s including the permalink dates. It probably works fine with URLs that don’t include dates. Wouldn’t using bloginfo(‘url’) for the admin URLs and bloginfo(‘wpurl’) for the plugin URLs solve the problem?

Comment by RT Cunningham — May 27, 2008 @ 4:03 am
@Suzanne, RT,

A fix is in the works and I’ll try to have it out today or tomorrow.

The problem is I’m using WP’s included thickbox.js file. They use it in the admin panel, so their original link is something like “../includes/js/etc.”, which would look the URLs you are seeing.

The bloginfo(‘wpurl’) is the install URL for WordPress. The bloginfo(‘url’) is the web URL. Sometimes these are different if a person installs WordPress in a sub-domain or in a sub-folder.

The solution may be me including my own version of the thickbox script. Thanks for bringing it to my attention.

Comment by Ronald Huereca — May 27, 2008 @ 6:15 am
Yep I suspected the same thing… I have my WP files installed to a sub-directory, but my site *appears* at the root. It’s a bummer there’s not some other way around that because to use the built-in thickbox files is kind of an added bonus. :-/ I’m not a PHP whiz – I wish I could be of more help on this one.

Comment by Suzanne — May 27, 2008 @ 10:37 am
@Sue,

The weird thing is, it worked for me on raproject.com, and not on ronalfy.com. Both are on the same host. I also had an issue with updating WP Super Cache on ronalfy.com as well, so I don’t think it’s plugin specific.

Comment by Ronald Huereca — May 27, 2008 @ 5:25 pm
@RT, Suzanne,

I updated the plugin (2.001) with the fix. Read below for the boring explanation of what was causing it.

When thickbox.js is read in, it assigns a load event. When this load event is run, it creates a new image and sets a SRC with the relative image (the reason for the weird 404 errors).

I tried to correct this by running my own load event and overwrite the image variables. Unfortunately, the thickbox one is run before mine, causing the 404 errors.

All I did was move my “variable over-writing” out of the load event and to the top of my JS file. Since the thickbox.js file is included before my JS file, the variables are already in scope. I just overwrite them using the same scope, then the thickbox.js load event runs and uses the updated image path. Fixed

Comment by Ronald Huereca — May 27, 2008 @ 5:28 pm
And I just tested it thoroughly. The 404 errors are gone. Thanks, Ronald! Look for an incoming ping or two tomorrow.

Comment by RT Cunningham — May 27, 2008 @ 11:12 pm
Thanks RT for the verification!

I’ll look forward to it

And I’m glad to have fixed the issue. Certain issues like these, unfortunately, do not come to fruition until after some live tests.

Comment by Ronald Huereca — May 27, 2008 @ 11:27 pm
I upgraded the plugin through the automatic plugin updater and everything has been going pretty well so far.

Comment by Jeffro2pt0 — May 28, 2008 @ 3:35 pm
Me too except for the occasional cached page, but that’s just cuz I’m too lazy to delete the cache

Comment by Suzanne — May 28, 2008 @ 4:34 pm
@Suzanne,

You’re not the only one who’s reported caching issues. Are you by chance running WP Super Cache?

Comment by Ronald Huereca — May 28, 2008 @ 10:29 pm
Nope – plain old WP-Cache but I wouldn’t consider that an issue. If a page is cached, it’s cached right? I would expect the bad call in the header to still be there on those pages.

Comment by Suzanne — May 28, 2008 @ 10:31 pm
@Ronald

Just an FYI — all the RSS and Security Key issues were cleaned up with the latest release. Everything seems to be working just fine. Thanks much!

nina

Comment by nina — May 28, 2008 @ 10:36 pm
@Suzanne (for some reason, keep wanting to write in Susanna),

One person using Super Cache has mentioned that non-logged in users don’t see their posted comments right away. I’m still trying to duplicate and hopefully fix it. When using the WP Cache portion of it, though, there is no issue.

@nina,

Yay! Good to hear, and you’re welcome.

Comment by Ronald Huereca — May 28, 2008 @ 10:40 pm
[...] had a very small hand in reporting an unusual 404 error bug at "Ajax Edit Comments 2.0 Released". There may be an issue with WP Super Cache, but I haven't seen any problems here. Of [...]

Pingback by WordPress Plugin: Ajax Edit Comments 2.0 — May 28, 2008 @ 11:40 pm
I think 2.0 is better than 2.0.0.1
2.0.0.1 don’t work at all on my admin menu.
So, I think 2.0 is better than 2.0.0.1

Comment by Rosyidi — May 30, 2008 @ 3:55 am
Sory. wrong version. I mean 1.1.5.1 is better than 2.0.0.1
I use wordpress 2.5.1

Comment by Rosyidi — May 30, 2008 @ 4:16 am
Rosyidi,

You’re going to have to be a lot more specific rather than saying something doesn’t work, or one version is better than the other.

Please fill out a support request and detail exactly what’s wrong, how to duplicate the issue, and attach screenshots if possible.

Thanks,

Ronald

Comment by Ronald Huereca — May 30, 2008 @ 11:59 am
[...] Wordpress. Go ahead, subscribe to our feed! You can also receive updates from this blog via email.Ajax Edit Comments, the Digg like comment editor written by Ronald Huereca has undergone a significant rewrite. For [...]

Pingback by Weblog Tools Collection » Blog Archive » Ajax Edit Comments Part Deux — May 30, 2008 @ 4:34 pm
[...] I also allowed Ronald Huereca to explain the new iteration of his popular WordPress plugin, Ajax Edit Comments 2.0 [...]

Pingback by WordPress Weekly Episode 18 | Jeffro2pt0 — May 31, 2008 @ 12:58 am
I preferred the “edit in place”; I don’t like the new thickbox screen.
Is it safe to use the pre-thickbox version?

BTW, thanks for this plugin. I’ve been using it for a long time.
Just one more thing: I’ve turned off button styling, yet the styled buttons still show.

Comment by johno — May 31, 2008 @ 3:18 am
@johno,
I received many complaints on the edit-in-place because admin wanted to click through on links. It’s one of the reasons I went with the all-in-one interface.

It’s safe to use the previous version. but no more updates will be released for it.

If you turn off button styling, they should still show in the admin panel, but not on a post.

Hope that helped.

Comment by Ronald Huereca — May 31, 2008 @ 3:34 am
Thanks, Ronald.
I’ve just re-read my comment, and it does sound a little ungrateful.
I think I will simply turn off styling and do the CSS myself, so that it matches the styling of my blog.
Many thanks again for a wonderful plugin.

Comment by johno — May 31, 2008 @ 4:01 am
This plugin is awesome.
But I have a problem.Buttons are not show in post area although button styling is on.Just letters.

Comment by collapse — May 31, 2008 @ 6:32 am
@johno,

Don’t worry about it. I figured there would be users who preferred the old plugin.

If that’s the worst I’ll hear about the plugin, I’m doing good

I appreciate the feedback.

Comment by Ronald Huereca — May 31, 2008 @ 12:26 pm
Just wanted to thank you for this plugin. This version has cleared up an error that has driven my site admins and I crazy. We weren’t able to use the Reply button in the old (1.0.X) version unless we completely logged out, but this version seems to have cleared up the problem completely.

Also, after adding this plugin, comments increased substantially on my blog due to the fact that the commenters could more easily communicate amongst themselves, which I think is a very good thing! Fantastic work, seriously.

Comment by DB Ferguson — May 31, 2008 @ 2:02 pm
@DB,

Thanks! I was almost expecting a “but…” in there as Sue mentioned above. Glad to receive such positive feedback.

@ALL,

I put out a small release. Viper007 and I talked over e-mail and I’ve decided to go back to storing security keys as custom fields. The concern here is the inflated post IDs, which is a valid long-term problem.

The problem with custom fields in the old version was that they would show up when editing a post. Viper informed that that putting an underscore prefix in the meta key would hide the fields. After some testing, I found this to be correct. So I’ve decided to go back to custom fields, which is the more logical place (IMO) to store these. As always, security keys can be cleared in the admin panel options.

Also of note is new RTL (right-to-left) stylesheets for languages that are RTL. The only language supporting this right now is Arabic, but I hope to add more soon. I just need a heads up from translators if their language is RTL.

Comment by Ronald Huereca — May 31, 2008 @ 2:07 pm
[...] Ajax Edit Comments 2.0 Released | The Reader Appreciation Project (tags: wordpress plugin comments) « links for 2008-05-30 [...]

Pingback by links for 2008-05-31 « RabiFoot at wordpress.com — May 31, 2008 @ 4:30 pm
Ronald…you’ve outdone yourself with the latest version. The editing buttons on the comments are a great UI improvement. In the 1.x version, I disabled editing directly on the comments because it would open the editor if I clicked accidentally. I did all required editing on the edit-comments page. Now I use the buttons! Great work and thanks again!

Comment by John P. — May 31, 2008 @ 5:53 pm
[...] new AJAX Edit Comments has been released, and the creator has remade it from the ground up. The interface has changed, it’s cleaner [...]

Pingback by The New AJAX Edit Comments : GoBloggin’ — June 1, 2008 @ 8:39 am
I’ve installed the plugin on several of my blogs. Neat one!

Comment by Pinoy Teens — June 1, 2008 @ 11:28 am
@John P,

Thank you. From a long time user like you, it’s nice to hear that you like the new changes and that you find it more user-friendly.

Comment by Ronald Huereca — June 1, 2008 @ 3:52 pm
Thank you for a WONDERFUL plugin! I absolutely adore it â€” including the latest version!

Comment by NEA — June 1, 2008 @ 10:10 pm
It’s time I had a plugin that can do this as I often need to change or add something to a comment I have made myself on other blogs. This looks like a great plugin and I hope to use it on all my wordpress sites.

Comment by Terence — June 2, 2008 @ 3:59 pm
[...] the WordPress Ajax Edit Comments plugin and I have to tell you that I’m quite impressed with Ronald Huereca’s work. The Ajax Edit Comments (AEC) plugin makes editing comments super simple for site visitors and [...]

Pingback by Ajax Edit Comments, WordPress Plugin Review >> PiXELWiT — June 5, 2008 @ 10:13 am
[...] the WordPress Ajax Edit Comments plugin and I have to tell you that I’m quite impressed with Ronald Huereca’s work. The Ajax Edit Comments (AEC) plugin makes editing comments super simple for site visitors and [...]

Pingback by Ajax Edit Comments, WordPress Plugin Review >> PiXELWiT — June 5, 2008 @ 10:13 am