Abigailm

If there is a difference between how things appear in a child theme than in the main theme, that would be due to some specification in the child themes stylesheet. Because Evolve developers often make changes to the main theme stylesheet with upgrades, that means that sometimes specific style specifications in a child theme will sometimes stop working.

So you need to use the developer tools in your browser to find out what is stylesheet specification controls the element that is not displaying properly for you.

I assume that you currently have the parent theme activated, as when I visit your site I do see line spaces between the paragraphs. (and not what you posted for your screenshot of the child theme).

From the parent theme, it looks like that comes from applying
margin-bottom:10px to the p element.

I would suggest reviewing your child styles sheet for any specifications that would impact spacing between elements, as it is likely that there is something overriding the parent theme’s specification for the paragraph margin bottom.

It probably depends on the site, because I didn’t experience any problems with search ranking on my sites. However I rolled things out more slowly — first setting up SSL & testing it, then adding to my Google search console and also updating incoming links on other resources (such as social media accounts, etc.) — and only switching to forced (always use https) after several weeks. So this gave plenty of opportunity for indexing.

I’d note that I manage a very busy site that is indexed by Google very frequently.

I did need to take my time testing in any event, to make sure that I had caught and resolved all mixed content errors. This was a big project on some of my larger and more well developed sites.

Jory, the developers might be missing your question because you are reviving an old thread – but their web site is http://www.itthinx.com/ and their email is written on the “Contact” page of their site — so that is probably the best way to initiate communication.

I like your idea, by the way. It is definitely something I would use.

Yes, once you have testified to verify that https:// works for our site, then the next step is to change WordPress settings to https://

However, that won’t prevent people from linking or accessing your site at http://

If you are want to force https, then you either need to set up an .htaccess mod rewrite rule on your site, or add an “Always use https” page rule via Cloudflare. Before you do that, however, I’d suggest checking your site for mixed content errors — that is something that may happen on any page that has an embedded image or script loaded from a nonsecure source. You will find those by checking for broken lock icons on your browser.

The cloudflare plugin will fix some of those by the automatic rewrite option, but it will only rewrite the links that the plugin can verify are available via https — so in my experience it won’t catch them all.

Please note I am no affiliated with Cloudflare — I’m just another user who has been through this myself, and I noticed that you asked a question 3 weeks ago and never got a response. The Cloudflare staff is usually excellent at providing support, but I guess your question got accidentally overlooked, and I thought I’d try to help out to at least get you started with the process.

@timerewinder – I manage multiple sites and experienced the same issues on upgrade. Are you using a caching plugin?

I am running WP Super Cache on the sites that had the problems. I solved the problem on all sites by following these steps:

a) Deactivate SpamShield
b) Delete Cache (from the WP Dashboard –> Settings –> WP Supercache)
c) Reactivate SpamShield

Also, as to your other question — there is a WP plugin called WP-Rollback available here: https://wordpress.org/plugins/wp-rollback/ – it makes it very easy to rollback to previous versions of most plugins and themes and I highly recommend it as a utility for all sites, as it makes it very easy to revert to earlier versions whenever you encounter problems.

You’ve already multiple times that you don’t want to cooperate with our support process.

No, I told you that I tried to use the form and it generated an error message and would not allow me to submit. Just as the user who started this thread reported.

As far as I can tell there is no alternative

I have experienced this particular form-use problem with SpamShield upgrades (the Javascript/cookie error reported by @kennychw) on multiple sites over an extended period of time, as long as I have been using Spamshield.

I tried an alternative plugin – Anti-Spam at https://wordpress.org/plugins/anti-spam/ — but experienced similar issues there. I chose to continue using SpamShield because of other, additional features. I am aware that it appears to be a due to caching plugins on the sites I manage, complicated by the fact that many of my sites are also on Cloudflare — so there are both local and cloud-based caches to worry about.

You could have reduced all of that to 15 minutes instead of an hour if you had simply contacted our support team

You won’t even acknowledge that my problems exist– and I doubt very seriously that I would get a response from a support request within 15 minutes. Additionally your hostility and rudeness to me and to other posters in an open forum makes me very reluctant to communicate with you privately. As I have posted before I have no interest whatsoever in debating you.

The reviews are an odd thing to subscribe to…that requires a bit of extra work.

I have never subscribed to the reviews, just the support thread at this page — https://wordpress.org/support/plugin/wp-spamshield/

Subscribing to the support threads on wordpress does also seem to automatically include the reviews but I can’t figure out how to unsubscribe from those, so generally I just delete emails that appear from the subject to be reviews. However, I can’t tell the source of any WordPress email from subject headers – they all just contain the identical notation: [WordPress.org Forums] – and I filter on that. I can’t even tell before I read the emails which plugin or theme they are referencing — though obviously I knew from the subject for this particular thread (“Version 1.9.9.9.1”) that it was this plugin, as no other plugin I use has such a long chain of versioning digits, and I had completed the upgrade to this version on the same day as I saw the topic.

I do stay alert to emails that make specific reference to new version upgrades to plugins and themes as a way of keeping informed about specific problems I might otherwise not become aware of– and I also do regularly contribute to threads when I am experiencing or have experienced similar problems and have information or suggestions to contribute.

• This reply was modified 9 years, 3 months ago by Abigailm.

I saw this today too on most of my sites. This is actually a fairly common problem with updates to this plugin — one reason why I have disabled automatic updates throughout. I also use WP Super Cache.

Here is what seems to work for me:

1) Disable the plugin.
2) Delete the cache from the admin settings for WP Super Cache.
3) Reactivate the plugin.

If you are using a different caching plugin, I’d suggest the same thing. Same deal if you have Cloudflare – depending on configuration you might need to purge cache there as well.

One of the reasons that SpamShield is so effective against spam is that it is a blunt instrument, requiring loading of specific javascript in order for visitors to post comments or submit to comment forms. So that eliminates most spam coming from bots. But the problem is that when the plugin updates, the javascript changes but the older script gets loaded from cache – and then there is a mismatch which causes the plugin to throw off that error message.

So basically that is something that can be fixed, but it needs to be tested with every update. For me it is a problem with posting comments and also on sites using Contact Form 7.