So, having completed the company move from Dubai Media City to Ras Al Khaimah Freezone, the next thing to do was update the web presence. This meant changing the company designation, FZ LLC, to the shiny new FZC and updating the Trade Licence number. On every web page. And the Facebook page. And this blog page. And the Linkedin page, and... Quo facto, it also seemed timely to heed Google's advice, that 2017 is to be the year of SSL, that sites using https:// with an SSL certificate would be favoured over 'standard' http:// sites. (The difference is mainly data encryption, which is a Good Thing in these heady days of cyber crime).
The nice people at uk2.net who host our site were only too pleased to sell us an SSL certificate and install it for free (though I secretly suspect that the installation cost might just have been covered by the purchase price!) which they did, two days ago.
Unfortunately, though the http site still worked perfectly, or at least as well as it did before, the new https access was a mess. All the right content but out of sequence and with wrong fonts and formatting. The fact that it was 'secure' was small compensation. Somehow, the https was blocking access to the CSS stylesheet, but why? I decided to sleep on it.
This morning I wakened up with the answer. I remembered that the site was referencing an external CSS file hosted by w3schools and had been doing so since before the days of https. Probably the secure protocol disallows pulling a file from an insecure site. Probably, too, w3schools would have been further ahead of the game than TriMedia in adopting https. Maybe the simple addition of an 's' in the stylesheet link would fix everything at a stroke? It did. Halelujah! (And I learned something).