Ron Dowd

Hi, I’ve just installed the plugin and am getting the same error. You can see it in the XML here.

Same happens for me, after updating the plugin. Does anyone have a suggestion for a good alternative for caching?

Will try reCAPTCHA v3 which evidently is hidden from users

ok, I’ll switch back to your plugin when you release the new version and will give it a try.

Interesting what you say, I was about to switch on Google reCAPTCHA v3 (which the other form plugin offers as an option), but will hold off for now.

Sure, I enabled the honeypot.

Just to let you know, the same format spam has started to appear on the other contact form. Maybe spam bots can now learn how to circumvent honeypots?

Yep sorry, I go through mailgun so didn’t want to risk SPAM to take me over the free threshold.

No spam with the replacement.

Hi,

Still getting an increased number of spams messages on one site, maybe three per day, which is not much I guess, but more than the 1 every 2-3 weeks I used to get.
Ron

Thanks, have switched it on. Will let you know how it goes…

Sounds great, I’ve used another contact form with a honeypot that seemed to be effective – but it will be great to stay with your solution which is so elegant and simple.
R

Timely reply, thanks…

I just received 33 messages on another web site (and have now temporarily commented out the contact form).

Host: 125-230-111-62.dynamic-ip.hinet.net
Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0

Thanks for investigating,
Ron

Despite several tickets and setting up staging where I could demonstrate the issue this was never resolved for me. I’m happily using Simple Cache instead: https://www.ads-software.com/plugins/simple-cache/

I have the same problem, “Save Draft” takes 8-10 seconds. I switched on the Query Monitor plugin and it shows that 6 – 8 seconds are taken up by HTTP POST requests to check for WordPress Core and Theme updates. On every save!

And thanks for your response @hristo-sg. I’m not sure why your response wasn’t showing up on the forum.

As I’ve said to @ivanatanasov, I’m happy with the way things are, I just don’t understand how it’s working and that concerns me.

• On my site, the SG Optimizer Force HTTPS setting is OFF.
• A warning appears on the Force HTTPS page saying “Warning: It seems you’ve been using another plugin or manually configured…”
• All internal links are working correctly for HTTPS.
• Any external link I specify that’s HTTP gets changed to HTTPS (I wasn’t so happy about that but now have implemented workarounds to link out only to HTTPS sites.)</>

So what’s doing the rewriting of links to external sites?

But having said that, and being happy with the way things are, I still don’t understand the behaviour.

(@ivanatanasov) you say:
“If you plan on accessing your internal links with HTTPS and the external resources with HTTP, it will be better to turn off the Force HTTPS functionality of SG Optimizer. Then, once you can apply external resources that support SSL, you can turn it back on again.”

But the Force HTTPS functionality on my site IS turned OFF at present*. So why do external links get changed to HTTPS?

* On the SG Optimizer Force HTTPS page, the cross x is showing (which I’m assuming means it’s OFF). There is however a comment on the page saying:

“Warning: It seems you’ve been using another plugin or manually configured your WordPress application to work over HTTPS. Please, disable all SSL forcing plugins and remove all .htaccess rules regarding SSL before you enable the option in order to avoid potential issues.”

Maybe this is something that SiteGround has configured manually for me? As I’ve said, I’m happy with things as they are, I just don’t like not understanding why it works as it does!

So thanks for not making any changes to my live site and thanks for your attention to this.

Thanks for your responses guys.

I’ve now made changes to my site so I only link out to HTTPS web sites, so I’m happy to leave things as they are.