Great! All errors gone! Thank you for your help, dear Ciaran.

Best, Adrian

Hi Christa

Could I ask you to update your template once more as we have just applied both fixes to the template download.

Ciarán

Dear Ciaran,

Thank you for your kind reply. Unfortunately I had deleted the default template and fail to reinstall it.

Web Console shows me the following error (on each page of my website):

[Warning:Invalid argument supplied for foreach()in/var/www/vhosts/http://website.com/httpdocs/templates/j51_caitlin/index.php on line 114]});});})(jQuery);</script> </body> </html>

Is it possible that it is related to template or maybe you could just give me an advice how I can solve this issue.

Thanks! Unfortunately I have no clue how to do this.

Best, Christa

Hi Christa

This error should be no way related to the update as the only change was CSS related. Just to confirm that this issue is template related could I ask you to check and see if the error persists if you enable one of the default Joomla templates (eg. Protostar).

Ciarán

Dear Ciaran,

Thank you! I updated the template and it looks perfect now! Unfortunately I noticed that the Console (Chrome) shows me an error that my website didn't have before updating (if I am not mistaken):
Uncaught SyntaxError: Unexpected token :

Is it possible to fix this?

Thank you very much!

Hello

We have just updated our Caitlin template amending the fallback fonts to Helvetica, Arial, sans-serif.

For details on updating your template may I suggest the following article... https://www.joomla51.com/tutorials/item/updating-your-template

Ciarán

Dear Ciaran,

Thank you for the clarification. Indeed it would be nice if you could let me know how to set Arial as fall back font.

Hello

Yes exactly. If the primary font is not available to the browser then the fallback font will be used. This currently is the Times New Roman font (browser default).

Ciarán

Dear Ciaran,

Thank you for your reply. Don't really understand what this would mean if I would set Arial as fall back. Would this mean that if browser A is not able to display the "normal" body font (Source Sans Pro) it would display Arial - but browser B and C would still display the "normal" body font Source Sans Pro (as they are able to)?

Hello

Personally I would say it is not a huge issue considering the current IE11 usage is less than 3% and dropping quite rapidly. Would you like to set a different font as a fall back? Eg. Arial?

Ciarán

Dear Ciaran,

Thank you for your fast reply. I found out that it is related to the tracking protection (which was turned on in IE 11). I just don't understand why this affects how the body font is displayed. Seems to be an issue with all google fonts except raleway.

Don't know if this is really a big issue? Do you recommend me to change the font or is there an easy solution or do the majority of people anyway not have this option turned on in IE 11?

Hello

Strangely we are unable to replicate this issue. Testing in IE11 your Source Sans Pro font is displaying without any problems. Is it the same issue for all Google fonts?

Ciarán