A couple days ago everything on my site was working perfectly then suddenly I started having all kinds of problems with broken formatting and I am not exactly sure what has caused it. I tried Stacks 3 and the latest version of Foundation but had some problems and decided it was better going back to Stacks 2 in the short term so I uploaded the old version again.
Everything was looking fine in the morning, then suddenly the formatting was all wrong on several pages but it didn’t even seem consistent and would change over time. I eventually traced it to an SSL issue. Chrome and Firefox are refusing to show various parts of the site because they are deemed to be insecure, so I contacted CloudFlare who handle the certificate and after a long wait they came back to say my site was linking to non secure elements that look like the CSS style sheets to me.
Later on I discovered they had reactivated my certificate with a new one just hours before and suddenly I had problems. If you go to https://colourmanagementpro.com/about/ for example in Chrome or Firefox you will see the formatting is a mess. Incidentally another site that I haven’t touched in months also done in Rapidweaver is suddenly having similar problems and that’s not done with Foundation.
CloudFlare are adamant that the problem is at my end and showed me a couple of screenshots showing from my page source. I am not linking to any http pages so it looks like the theme itself or something else. I am wondering if the spec for their SSL certificates has changed overnight.
I went onto the server via FTP and deleted the whole lot in case there was any coding left behind from my experiment with Stacks 3 and then uploaded my old site again from Rapidweaver but nothing has changed.
Can anybody see where I am going wrong here? I have attached a couple screenshots showing the areas of code that CloudFlare says are responsible. To me it looks like something has changed at CloudFlare or the specification of SSL has suddenly become much tougher and is breaking Rapidweaver sites. I am using their flexible SSL setting that should be quite forgiving.