@RachLewis Looks like you have an attempt at adding styling code that has gone awry. I can't say for certain where you added this but it appears to be footer code. (This could have been added directly in the page's header html (after the Weebly plugins and and custom javascript references) or in the site's SEO footer code. The problematic code is highlighted below (lines 5222 to the closing style tag in line 5228):
The myriad of problems include:
- An orphaned closing style tag on line 5222;
- Various "#SFctr" ids (default and hover state button ids) that indicate the id names but have no actual css style attributes indicated (and you're missing some comma delimiters between ids);
- Another orphaned closing style tag on line 5226;
- Yet more #SFctr" ids (that incorrectly follow the orphaned closing style tag noted above and also have some missing comma delimiters between ids) followed by a closing style tag (line 5228).
What you were probably trying to do here was indicate the styling for the #SFctr buttons and navigation links. Everything highlighted in the screenshot should look something like this (I've added line breaks between ids so you can clearly see where the comma delimiters should be):
<style>
body #SFctr button,
body #SFctr a.SFbtn,
body #SFctr button:hover,
body #SFctr a.SFbtn:hover {
[insert button attributes here]
}
body #SFctr nav a.SFsel,
body #SFctr nav a.SFsel:hover,
body #SFctr nav li.SFsel a,
body #SFctr nav li.SFsel a:hover,
body #SFctr nav > a {
[insert navigation link attributes here]
}
</style>Typically, you don't specify the default and hover states for an element within a single css attributes block so those curly brackets probably need to be separately applied (specify the default/hover state attributes separately). And finally, css is normally added to the header zone not the footer zone. There can sometimes be a need to late load css but I'm not sure that is necessary here given that these ids look to be custom.
The first thing you should do is remove all of the code highlighted in the screenshot wherever you put this and start again but with correct css syntax on the next go 'round.
