Tigr

Yep. Works nicely, a steadily increasing number of blocked spammers. Thanks!

Okay, I set it up, the forms are generated, let’s see what it will bring. Thanks.

Javascript? Heh, that figures. Why would I expect anyone to provide download links with javascript? Of course, javascript is switched off, as it should be, in my browser ??

Your site gives me “Invalid Plugin Request” errors for any beta plugin. What gives?

Wait, wait, assume nothing has changed, only the plugin was upgraded. It worked fine before.

1) SFS is slow sometimes but usually it does not stay slow. So far I did not succeed submitting any requests.
2) Remote file access? If you mean allow_url_fopen, then that’s disabled but it was always disabled. Did you change how you access SFS?
3) Checked. Key is correct.
4) IPV4
5) Both long and short messages result in the same message.

I tried resubmitting old spam that was in trash, the spam that was previously successfully submitted – same thing.

The problem is the same on both network (multisite) and single standalone WP sites.

And the spammer does not show up in SFS at that.

WordPress automatically deactivates the plugin because stop-spammer-registrations.php is not there. The plugin now uses stop-spammer-registrations-new.php. All you have to do is to activate the plugin again.

Sure. As I say, first you had a problem of swamping me with data so that the relevant information was buried in a mountain of detail. Fortunately, that has cleared and I was happy for a while.

Now I thought that everything was fine with the website because there are no security alerts and everything is oh, so quiet. Suddenly I needed to investigate something and I went to the log. The log contained no information at all. It was empty.

I quickly switched to another site and that one had a single entry that read “5 events automatically deleted” dated an hour or so ago. And nothing else. So I did not have any log whatsoever on either site. Although previously they both worked just fine.

Now, we are talking about a security critical component here – the audit trail. I rely on it to do its job. When it does not or cannot do its job for some reason I expect to know about it right away. In this case, the plugin did not report anything to me and kept me happy by not logging (or deleting the info).

No logging is better than false logging.

No, in your case the problem is different. Notice how the server reported with “HTTP/1.1 404 Not Found”. That means the URL was not there when you called. I tried that URL and it works though, you may want to simply try again, perhaps your blog was new and their platform was not ready yet to serve your blog over rpc?

Ah, good catch. It did successfully post after I changed to https. Thanks a bunch!

3.4.5 does not address the problem, fails with the same message.

WP.com is extremely helpful as usual:

“That looks like a plugin for www.remarpro.com (self-hosted sites). Those aren’t available for blogs at WordPress.com. Instead, you could use Publicize to achieve a similar result”

You must be kidding. It all just started working now. Both old and new accounts are running smoothly, I can authorize and select the views.

So I suppose Google just screwed something and then repaired it. Thanks, Google, three hours of frantic searching, reading, trying weird tricks for nothing.

Sorry to bother y’all.
Cheers!

The old account gives error:

Last Error: 2014-11-26 07:52:04: exception 'Google_Service_Exception'
with message 'Error calling GET https://www.googleapis.com/analytics/v3/management/accounts/~all/webproperties/~all/profiles?key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:
(403) Daily Limit Exceeded' in /.../wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Google/Http/REST.php:79

Okay, I can sort of imagine that but not really. The website is really no to very low traffic.

Interestingly, the new account gives the same error:

Last Error: 2014-11-26 07:55:36: exception 'Google_Service_Exception'
with message 'Error calling GET https://www.googleapis.com/analytics/v3/management/accounts/~all/webproperties/~all/profiles?key=xxxxxxxxxxxxxxxxxxx:
(403) Daily Limit Exceeded' in /.../wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Google/Http/REST.php:79

This is a freshly set up account. It cannot exceed limits because it was never used.

Any thoughts?

Right. Removed the plugin, dropped the tables with audit and wsal, removed all options with wsal in them. Reinstalled the plugin, now seems to work without errors. There must be something messed up sometimes during update, that’s why you cannot reproduce it.