sugarcane

@simon-deziel

Hi Simon,

I found your post as I am having the same difficulty as you in subscribing to the announce mailing list. Frustratingly, the instructions at the link you listed do not work for me either.

I found the following post which was of help to me, and I thought it might help you also:
https://www.ads-software.com/support/topic/new-release-mailing-list/

Essentially, what I did as a workaround to not being able to subscribe to the announce mailing list was to subscribe to the www.ads-software.com news feed using IFTTT. When you create an account on IFTTT, you can set up a recipe to email you when there is an update on the RSS feed.

I hope this is of help!

Hi Surfdenis,

I don’t know the answer to this but I am looking for a solution to the the same problem. I tried found the following link which describes code how to change the sample size:
https://developers.google.com/analytics/devguides/collection/analyticsjs/field-reference#siteSpeedSampleRate

I tried putting the following code into the the Custom Code box in the ‘Google Analytics for Yoast’ settings (under the Advanced Tab):

ga('create', 'UA-XXXX-Y', {'siteSpeedSampleRate': 50});
(Inserting my tracking ID and changing the 50 value at the end to 100).

However, it didn’t work and even stopped by tracking from working at all. I installed a Chrome plugin called Google Tag Assistant which allows you to see the tag errors on a page.

I hope someone is able to answer your question for the both of us and I have subscribed to this topic. If I find an answer elsewhere I will post it here for you also.

Great! Thank you for you extremely fast response ??

@themadproducer

My hosting provider providers a feature in their settings panel to block access to the login page, which I have activated. I will followup up with them and check if it is blocking the login completely. When I check from another IP in a web browser I am blocked with a 403 forbidden error. However, in my apache access logs I see an entry from the offending IP showing:

“POST /wp-login.php HTTP/1.0” 200 3970
“POST /wp-login.php HTTP/1.0” 200 3970
“POST /wp-login.php HTTP/1.0” 200 1646 …

To my understanding the 200 codes indicates a successful post to the login page?

I will also try the apache block code you posted. Many thanks for you help!

@themadproducer
1) Yes
2) 3
3) What I meant is my wp login page is blocked at the server level (Apache) to only allow access to my own IP. No other IPs have access to the login page.
4) Amount of time a user is locked out is set and is working as expected

I am trying to understand why, if both login avenues are blocked (wp login page and XML-RPC), how is it possible for anyone to have the opportunity to attempt a login in the first place?

The fact I am getting warnings from Wordfence that a login attempt has been attempted and blocked indicates that either one of those 2 login avenues are open (but they’re not) or there is a 3rd avenue available that I am not aware of.

Thank you for your reply and ideas to help unravel this mystery!

Hi Bear 29a,

I also get the same error when trying to download a backupbuddy file. I am
also hosting on Digital Ocean (using the WordPress installation script using Ubuntu 13.10). Did you ever find a resolution to this issue? I looked at the instructions given by lifeinthegrid above, but could not bring about a fix.

Cheers!