I think @Webdongle "gets the gong" for explaining how to fix this issue.
Even I learnt a thing or two from it!
marksfish wrote: ↑Thu Jan 10, 2019 9:24 am
Thank you for your reply. I will look in the template.css file. Do I just place the code anywhere in the file, or must I overwrite some other code?
I don't know how many times I have written this, but at the risk of repeating myself again, as far as is humanly possible—and human nature is always tempted to do the wrong thing—never change any files that are created within software that you, yourself, haven't written. If you must make your own customised changes, then find other ways to override whatever it was that was done by people who write software (including CSS).
Let's look at the whole situation: we're discussing
Protostar. While there are few changes made by the Joomla developers as far as
Protostar is concerned, changes do happen. If people have modified the original Protostar files (including the file
../templates/protostar/css/template.css) and they update from one version of J! to another—and the process replaces that file—we get the inevitable "My J! website looks like garbage since I updated J!" litany of complaints.
Protostar allows people to add their own custom CSS. This is done by creating a file named
user.css. The whole path is, therefore,
../templates/protostar/css/user.css. This file is not replaced when one updates J! (because only originally-supplied files are affected by updates and this file was never created to begin with).
So, when people write—even with good intentions—to edit the file
template.css file "if you do not update your template", I cringe. Maintaining a website doesn't mean that people will not—intentionally or otherwise—"update their site template". Maintaining a website means that people should update their software (after testing of course on a test site) when new software is released.