inge12

I have the same issue, except that my editor window is HUGE – many pages long. And resizing it does not “stick.” Even after saving a post, the editor springs back to the HUGE size.

Information for the plugin author re the first error message is here:
https://make.www.ads-software.com/core/2012/12/12/php-warning-missing-argument-2-for-wpdb-prepare/

On another blog WP ThemesPlanet suggested:

$results = $wpdb->get_results($wpdb->prepare($query));

with this one:

$results = $wpdb->get_results($wpdb->prepare($query, $args=null));

I replaced
($query)
with
($query, $args=null)
in both lines specified.

And it worked, because the error message went away and WP Super Edit actually seemed to be called for the editing window. (Before the edit it was just ignored.)

But now I’m getting new messages:

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/ssnet/public_html/wp-content/plugins/wp-super-edit/wp-super-edit.php on line 152

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/ssnet/public_html/wp-content/plugins/wp-super-edit/wp-super-edit.php on line 217

And I’m stumped again. Need to disable plugin.

No error messages for other plugins so far ..

One person suggests the following:

Contact the plugin creator. They need to update their prepare statement with a 2nd argument.

Sounds simple enough …

Note that the error message I got is specific for WP Super Edit. Did you find any other plugins named?

I imagine there are a lot of WP Super Edit users.

petro23

I just checked your site in Chrome, and the icon displays correctly. I’m viewing in Windows Vista.

Sometimes a different operating system makes a difference.

If you cannot login to your blog because of a plugin — any plugin — you need to delete the whole directory with the plugin from your server.

To do that, use FTP (like Filezilla), login to your site and go to
wp-content/plugins/

There you will see a folder entitled
alphaomega-captcha-anti-spam

You can delete the whole folder, and you will get your previous setup back, and you can login the usual way.

Renaming the folder would probably do the same thing.

If you do not have FTP access, you need to ask an administrator to do this for you.

Thanks for the response. I will install the plubin again on a test site and see how it goes.

However, I’m still wondering why the plugin would need a “commenting too fast” check when automatically filled invisible fields will stop the spam bots.

For me, the “lighter”/least processor-heavy a plugin is, the better. If there are redundant methods of stopping spam, it would only seem to use more processor resources.

Thank you for the reply.

Is it necessary to have a “commenting too fast” check when you have invisible fields to trap bots? If the invisible field method actually works, it should not be necessary.

It was not just my comment that got lost, but another user’s good comment went to the spam bin. If I had “spam” blocked it would just have vanished into cyberspace.

It is fairly common for our users to compose their replies in Notepad or Word and then paste them into the comment form. And they might just load the page for the purpose of commenting. However, I’m wondering if there’s another quirk that is the issue.

I’m also wondering — is it not possible to save the comment on the user’s computer, so it can be retrieved by the <back> button?

As it is, I cannot use this plugin, since comments are the life blood of our blog.

It sounds so promising …

It’s too bad that this plugin seems to have been abandoned.

It would be great to have the added option of deleting spam instead of writing to database.

Someone keeps marking this thread as “Resolved.” I wonder who that might be?

I’ve been testing more spam plugins. I found NoSpamNX, which looked really promising. No javascript required and no math. Local blocklist, etc., much like Todd’s plugin.

I seems to catch all spam as well as Akismet does. It seemed to work well on a test site — just as Todd’s plugin worked well on initial testing. (I have not yet done extensive testing on a test site.)
HOWever, NoSpamNX also produces false positives from comments that are thoughtful and have no earmarks of spam. It shouldn’t happen with that plugin, according to the posted design of the plugin.
The difference is that the author of NoSpamNX did not claim “No false positives.”

Back to Math Reloaded for the time being. It’s a bit of a bother for those who comment, but better than losing comments.

Just wondering whether Spam Free WordPress requires Javascript. Instructions don’t say so.

While I was writing the comment above, someone else’s perfectly good (not bird-brained!!) comment was shunted into the spam folder.

With the amount of spam we get, it is easy to miss good comments in the spam folder, and that’s really why I wanted to use your plugin which could block obvious bot spam.

AFter writing I did not get false positives with Akismet during several months, I got 6 false positives today!

Just sharing in the interest of transparency. ??

Still would love to think that Todd’s plugin works as promised. It would make life SO much easier.

Am testing the “Math Reloaded” plugin at the moment. Looks promising: Much easier to read than most CAPTCHA’s, and I’m not sure we need comment from people who can’t do 12+7=?

Plugin does not require Javascript, unlike the Growmap plugin, which uses a simple check box, but requires Javascript to be enabled.

I noted the following in the FAQ

Is Spam Free WordPress compatible with other comment spam plugins?

Yes, however, other comment spam plugins will cause false positives, so it is best to disable all of them, including Akismet.

I figured that “false positives” would not be a problem, if they ended up in the spam folder, as they do with Akismet–especially if the number of spam comments were reduced.

Hence I ran Spam Free WordPress with Akismet.

The problem was that the comment was rejected/lost without ever getting to the spam folder (as WordPress Spam Free appears to be desiged to do) Thus neither the comment writer nor the moderator had any way to retrieve the comment.

Todd, you wrote:

Everything you said in your reply proves you never read a word on this page, https://www.toddlahman.com/spam-free-wordpress/,

As a matter of fact, I read every word. Normally, you “troubleshoot” when there is a problem. If the first remedy works, that’s where you stop.

There was no problem when I tested the plugin by leaving comments that had been caught by Akismet, other than that Spam-Free did not filter them out. These may not have been comments left by bots, but Akismet is smart enough to flag them as spam. (And, by the way, in thousands of spam comments over the last few months, we have not had a false positive from Akismet. I think Akismet “learns” from comments manually marked as spam.)

But the point is that you advise:

“To test Spam Free WordPress, logout out of your WordPress account, and try to leave a comment.”

I did that, and it worked fine. So no more testing was presumably needed.

I would not have known that serious comments are blocked by Spam Free if my husband had not worked so hard on a long, serious comment, only to see it vanish into cyberspace. In your plugin, the “back” button should lead back to the original comment, which should have been stored in a temp file on the computer. But it doesn’t.

Furthermore, you do not warn people to do extensive testing for this sort of problem.

Your threatening does not demonstrate that your plugin is as you describe it:

“IThis trouble is further compounded, when you recommend in a public forum, that others avoid using my plugin on a false and uniformed basis while also making false accusations. I consider your accusations to be serious, and so should you. I will respond accordingly if you continue your attacks.”

Characterizing me as ignorant does not demonstrate the value of your plugin.

Characterizing the description of my experience as “your attacks” does not demonstrate the value of your plugin.

It seems to me that as long as you characterize users of your plugin as ignorant and the telling of their experience as “attacks,” rather than figuring out how you can improve user experience, people should be very wary of using any of your plugins.

It also seems to me that by forcing people to come to your site for support, you are controlling what appears on the WordPress forum, and thus WordPress users cannot tell how many problems people actually have with the plugin.

The bottom line is this:

Even if it worked as described, Spam-Free is not the only plugin needed to control spam. Akismet is still needed to catch manual spam.
Bloggers who value meaningful comments should do extensive and thorough testing before installing your plugin on a live site. (My mistake was that I only did the recommended test.)
Yes, Spam-Free does a good job of blocking spam with a lot of links, and that will reduce the amount of spam that needs to be deleted.
HOWEVER, it is not true that it produces “Zero false positives.” That is actually too big a claim for anyone to make, because it cannot be proven. However, it can be disproven by just one false positive–which is what I experienced.