belamer

Thank you for your insight.

In our application, and this may well be the case for others, inserting the brand in the title will not work as it would be repetitious as the brand is the domain itself. We have tested and seen almost immediate, not so nice results. TSF’s reminder about not setting site title I can ignore and have got used to it, no need for any filter but thanks.

I’ve gone ahead and purchased the license for 4 years after carefully reviewing and testing other SEO plugins.

Thanks. Look forward to the link.

Same critical fail here. I noticed people were sending messages through FB. So went in to test Contact Form 5.4 and it gives a new forever spinning wheel and nothing happens. Reverting to 5.3.2. and it works perfect as before. Please fix this! Use Perfmatters to unload Contact 7 script everywhere except on Contact Page.

I visited the Have To Host site and see you are not using a CDN. The icons look tiny on laptop.

• This reply was modified 4 years, 1 month ago by belamer.

I have the same problem since the Genesis StudioPress Simple Social Icons Plugin was last updated to version 3.0.2 a little under a year ago.

The Genesis Studio Press creator Brian Gardener sold out to WPEngine. The plugin has not been updated since then.

I have posted this problem on the Genesis Studio Press FaceBook support page and expect it gets resolved ASAP. I will also try to post it on the GENESIS SLACK forum.

The only solution for now is to exclude the plugin from your CDN thus:

/wp-content/plugins/simple-social-icons/(.*)

This hack regretfully slows down our websites as it cannot be cached on our CDN.

I am unable to get WP Supercache working with Amazon CDN on https. It works on my other domains with http, but if I changeover a site to https it flops. I have spent many hours re-installing, double checking my CDN setup etc. I have reluctantly had to remove this plugin and go back to W3 Total Cache.

I have used this plugin in the past, and tried it again after abandoning it for a couple of years. WP Super Cache is lightweight and easy to configure, but it does not work with HTTPS on Amazon Cloudfront. I have spent hours trying to make it work with no success. Using W3 Total Cache the setup for AWS is easy. Simply enter your credentials, and W3 Total Cache atomically connects to AWS and creates the distribution and starts working. WP Super Cache uses a different approach. You have to create your CDN distribution yourself, and then enter your AWS Cloudfront address and it does not work. It is a pity but I have had to go back to W3 Total Cache.