Christopher Finke
Forum Replies Created
-
Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Improve interaction observingBefore doing that, can you check if you change the
250in the Akismet event code to500, does it work then?Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Improve interaction observingYes, I’m looking into this, although I don’t have access to a copy of that theme. Is the website available publicly so I can test it myself?
Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Improve interaction observingDo you happen to be using the Listable theme? If not, what theme are you using?
It looks like wpDiscuz will be addressing this; I’ll watch for their fix and check whether we can improve Akismet to handle similar situations more gracefully.
That’s great! Thanks for the update.
I’ll do some testing to see if I can reproduce this, but can you tell when these warnings appear? Is it immediately after submitting a new comment?
Given that you’re also getting warnings from core code, I don’t think Akismet is the cause of this. My guess would be that another comment is storing data in the comments database table but not populating comment_post_ID, comment_author, comment_author_url, and comment_author_email, which both Akismet and the code code expect.
You could find out by just seeing what information is in the wp_comments table (if you have that ability) or by listing your plugins here, and we can probably determine it.
Thanks; this fix is in version 5.0.1, which is being released right now.
It will be in version 5.0.1, which will be available in the next hour.
If you’re interested in trying a fix right now, you could paste this chunk of code into akismet-frontend.js right after the line
var form = forms[i];, which is line 45 in version 5.0:var formAction = form.getAttribute( 'action' ); // Ignore forms that POST directly to other domains; these could be things like payment forms. if ( formAction ) { // Check that the form is posting to an external URL, not a path. if ( formAction.indexOf( 'http://' ) == 0 || formAction.indexOf( 'https://' ) == 0 ) { if ( formAction.indexOf( 'http://' + window.location.hostname + '/' ) != 0 && formAction.indexOf( 'https://' + window.location.hostname + '/' ) != 0 ) { continue; } } }That should prevent the interaction observation code from being run on any forms that submit to other sites, like credit card forms. If you try it, can you let me know whether it works for you?
Are you using the “Direct Post” integration method in the payment plugin?
I’ve committed this change to Akismet trunk; are you able to install it (from http://downloads.wordpress.org/plugin/akismet.zip) and confirm whether it solves your issue in CWV?
Thanks for the report; I’m looking into this now.
I think this question would be better suited to the WooLentor forum: https://wordpress.org/support/plugin/woolentor-addons/
At this point, without cooperation from Listable, I don’t think we can fix this, so I’m going to close this thread. But if you do hear back from them, please reply here and we’ll see what we can do.