Christopher Finke
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Akismet causes CF 7 to hang on submitThis is a combination of two issues:
1. Contact Form 7 is still calling
akismet_get_key, which was deprecated in Akismet 3.0.2. You have
WP_DEBUGenabled, which is causing the deprecation notice to be output during the AJAX call that handles the contact form submission.So: enabled
WP_DEBUG, downgrade to Akismet 3.6, or wait for Contact Form 7 to update their code to use the new Akismet methods.Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Verbose logging from AkismetThe logging function called on line 644 only logs if
WP_DEBUG_LOGis enabled. Disabling that flag should disable the Akismet logging too.Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Remove Akismet WidgetRaise the priority argument of your
add_actionso that the widget is guaranteed to be registered when you try to unregister it:function removeAkismetWidget() { unregister_widget( 'Akismet_Widget' ); } add_action( 'widgets_init', 'removeAkismetWidget', 11 );The call to wp_print_scripts has been removed as of https://plugins.trac.wordpress.org/changeset/907986/akismet/trunk
Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Stats not showing since last updateIf you try to visit this page: /wp-admin/options-general.php?page=akismet-key-config on those sites where Akismet isn’t appearing, what do you see?
Forum: Plugins
In reply to: [Inline Preview] Broken in WP 3.9 ?Sorry for the inconvenience; version 4.2 is out now and compatible with WordPress 3.9.
Forum: Plugins
In reply to: [WassUp Real Time Analytics] Call to undefined method Akismet::isSpam()Akismet developer here; you are correct — Wassup should be prefixing their class names with something guaranteed to be unique to their plugin. “class Wassup_Akismet” would be more appropriate.
Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] Stats not showing since last updateSimplySan: Do those other 6 have Jetpack installed? If they do, the Akismet stats page is under the Jetpack menu.
That still appears to be the same All-in-one Calendar bug, but just triggered by updating a plugin. The newest version of All-in-one Calendar doesn’t appear to have the same problem, so if you can delete your current copy and install the newest, you should be good to go.
The error log would be on your MT server; I think these are the correct instructions for finding it: http://kb.mediatemple.net/questions/732/Where+are+the+access_log+and+error_log+files+for+my+server%3F#gs
It looks like error logs might be disabled by default; if that is the case, enable them, and then visit one of the white-screening pages, and then view the log.
Where are you looking for the error log? Specific pages don’t have their own logs; it would be in the PHP error log for your server.
The next step would be getting ahold of the error log and see what errors show up there when you try to access any of the pages that are white-screening.
For what it’s worth, I installed and activated all of those plugins and wasn’t able to get a white screen. My top guesses are either that you’re running a version of WordPress that your host has modified, or that a cache somewhere thinks that some plugin files exist that really don’t. Either way, contacting your host is the way to go.
The next step I would take would be to contact your webhost and ask them to restart Apache (or whichever Web server software you’re running) on your site. In the case that there is some cache software running that you’re not aware of, that usually helps to fix problems with it.
Just removing the code from akismet/akismet.php should be sufficient.