@all: This case (except for RonStrilaeff’s reply) has been discussed 4 months ago and the link in Network admin is still broken, leading to “Access Violation” error message. Haven’t you fixed this yet / updated Akismet plugin for such long time?
@ronstrilaeff: No way, their going to do this, because this is bad. Most people uses WordPress Network to manage own network of blogs from one general dashboard (with registration of new sites disabled by default). But think about those, who run sites like WordPress.com, which are open for registration of new sites. Admins of such networks for sure require, that end-point users enter own Akismet API key as they don’t want hits from user sites to enlarge hits counter of their own Akismet account. Especially, if they’re enterprises and had to pay for API key and will have to pay extra in pay-per-call mood, once their network overall hits count passes certain limit (of 100k hits per day, if I’m not mistaken). So for such installations having abillity of entering different API Keys per different sites is surely most welcome.
@trejder Good point. That does make sense for someone who is setting up a mini host or community of bloggers as the original design (ie: wordpress.com) was conceived. I can live with entering it for each of “my” subsites. Thanks.
well i will let the plugin on the server deactivated untill a update come across to fix this. i understand the aproch of having independant API for each blog on MU but NOT ALWAYS is the same case. some people run multisites with really simple settings to their users to avoid clients/users not wp savy to let them know they need to signup for an API key and put it there and so on (i want to avoid that). I was looking foward to config the whole network with 1 API with this plugin http://wordpress.org/extend/plugins/akismet-wedge-for-mu-plugin/
anyway, ill wait. please uptade this threat when it get fix please or IF a workaround happend or else.
thnx guys for stepping!
This solution looks great (though I’ve already entered my Akismet API for each of my network’s site). But it doesn’t change the fact, that bug menioned in this thread should be fixed ASAP! :]
Hello, I am still not sure what is the conclusion. Please could you summarize?
I cant see the akismet in my WordPress multisite dashboard (either network or individual site). It used to work earlier.
Thanks for your help.
great post.
thanks for your help
OK my solution, (if it may help someone else) to fix it, was to reload the akismet folder in plugins directory with latest akismet files. It’s fixed.
Same here. Weird issue that keeps coming up from time to time. Not sure because I usually find out later but it seems to start after a WP core upgrade.
Tried about anything but only after:
1. Deleting the akismet plugin folder
2. Reinstalling it throught the WP plugin installer
3. and then Network Activate it (this was not needed before!?!)
all is working again…
