Just an update on this.. I ran into several problems mainly to do with external content being supplied using scripts using http links. http content cannot be displayed in https pages without causing insecure contents warnings.
And believe it or not the main culprits were Google (AdSense links), Google search bars, Ebay partner network, and Photobucket links to images that our users had posted within the threads.
The Google AdSense content was easy to resolve by updating the scripts, Photobucket image linking is another one all together.
Firefox, Chrome and Safari all caused browser issues resulting in some changes to files, and IE users who do not have 'show mixed content within pages' enabled found that warnings kept being displayed for insecure content.
One thing I did find useful though is the developer tools within Firefox as it allows you to see the source of the errors as you browse your content which makes for fixing them a whole lot easier
The first line: <meta charset="UTF-8"> gives a character coding that speeds the loading of the pages up
(Edit : If using £ within your pages use the following if the £ sign displays as a ? <meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/> )
Forum goes SSL
Posted - 26 March 2017 : 15:59:49
especially allowing members to use external links.