your host should be able to whitelist simple press… or to disable: http://stackoverflow.com/questions/12928360/how-can-i-disable-mod-security-in-htaccess-file
@mr-papa – I wasn’t thinking so much as the site url – rather more the query var sent with an update…thoughts?
ModSecurity has never been activated and the OWASP ModSecurity Core Rule Set was not installed. I also had previously checked the cPHulk Brute Force Protection for your IP 209.133.213.27 from which the downloads commence, and it is not listed. I also added it to the White List anyway, to assure connectivity. Thanks.
S. E. Ray said
ModSecurity has never been activated and the OWASP ModSecurity Core Rule Set was not installed. I also had previously checked the cPHulk Brute Force Protection for your IP 209.133.213.27 from which the downloads commence, and it is not listed. I also added it to the White List anyway, to assure connectivity. Thanks.
CPHulk only protects system logins. White or Blacklisting does not effect site access.
I’m not sure if this is the thread that we have been discussing the auto update on, but I want to announce that for the first time in many updates I was able to do the auto-update without any issues.
I haven’t changed anything with our server but perhaps one of the plugins made a change that corrected a conflict.
Did you guys change anything that might have corrected the issue?
PS.
When I went to log-in I saw that my membership had expired.
I think it would be a good idea to receive a notice that the membership is about to expire. Also, an auto-renewal would be great.
I believe we lengthened the timeout a little from 5 to 10 seconds but I think that is all. @mr-papa can confirm if there was anything else.
The membership plugin we use absolutely should send out an email a few days prior to expiration. In fact one or two people have complained that it did so. But we do appear to get the odd misbehaviour with it bit it seems to be random. Did you check spam folders etc?
We don’t really like the idea of auto-renewal. It seems a little pushy to me and we don’t really want to do that. But an email should have arrived. We probably need to open a support ticket with the authors of the plugin we use.
Did you see that you have got your pagination in PMs with 5.7.2?
I had planned to comment on this but have been too busy.
Upon the update to WordPress 4.6.1, I was immediately able to update the simple:press core and any modules using the built-in WordPress update feature. Clearly, WordPress changed something that remedied the problem. If it had anything to due with a change in simple:press, I would have had to download and install the updates manually at least once to achieve any change, but that was not the case, it was entirely related to the WordPress 4.6.1 update.
The only installation related detail WordPress modified in their update was there was an infinite loop in _wp_json_sanity_check() during plugin install that effected only some plugins.
Thanks!
Ah. Of course. I spent most of the day driving across country and am tired and I missed the obvious chicken and egg situation, You are right.
So good news all around by the sound of it.
a few versions back wp switched how the wp http api worked to use the requests library.. several updates for it were included in the last wp version so perhaps that helped indeed…
Yes, it must have been the wordpress changes since I do every single update as they become available.
In any case, no worries about the reminder. I just feel that you guys work hard and shouldn’t have to miss out on revenues for something as basic as this. 🙂
fiddlerman said
…………….When I went to log-in I saw that my membership had expired.
I think it would be a good idea to receive a notice that the membership is about to expire. Also, an auto-renewal would be great.
Yellow Swordfish said ………The membership plugin we use absolutely should send out an email a few days prior to expiration. In fact one or two people have complained that it did so. But we do appear to get the odd misbehaviour with it bit it seems to be random. Did you check spam folders etc?
We don’t really like the idea of auto-renewal. It seems a little pushy to me and we don’t really want to do that. But an email should have arrived. We probably need to open a support ticket with the authors of the plugin we use……….
Off subject again but since I posted the information a bout not getting a notice, I’ve been getting them on a regular basis even though my membership has been renewed for quite a while now. Received about 10 of them and just got another one today.
Hi fiddlerman,
Your Gold Membership with Simple:Press expired on October 5, 2016 and we are sorry to see you go.
If you wish to renew your membership, you can do so at http://simple-press.dev/store/account/
Thank you for your support!
The Simple:Press Team
My apologies. I think it is my local development version that is leaking. i turned all this off but refreshed my database a few rimes recently probably threw out the email before I could re-turn off the options.
If it starts up again can you let me know? Just in case the diagnosis of that s wrong. Again – apologies.
Happened again today. LOL
_____________________
Fri, 28 Oct 2016 02:17:42 -0700
Received: from 82-69-109-167.dsl.in-addr.zen.co.uk ([82.69.109.167]:52284 helo=Alice.lan) by s166-62-122-93.secureserver.net with esmtp (Exim 4.87) (envelope-from <andy@Alice.lan>) id 1c03IE-0003sx-7Z for pierre@fiddlerman.com; Fri, 28 Oct 2016 02:17:42 -0700
Received: by Alice.lan (Postfix, from userid 501) id CD0464494BBD; Fri, 28 Oct 2016 10:16:44 +0100 (BST)
Delivered-To: pierre@fiddlerman.com
Subject:
Expired Simple:Press Membership
___________________
Hi fiddlerman,
Your Gold Membership with Simple:Press expired on October 5, 2016 and we are sorry to see you go.
If you wish to renew your membership, you can do so at http://simple-press.dev/store/account/
Thank you for your support!
The Simple:Press Team