zk379 Posted August 2 Share Posted August 2 Everything was working until I checked the site today. Custom code is as follows: //Font Pact Trend Effect Callback @font-face { font-family: Butler; src: url(https://static1.squarespace.com/static/63acfcc394c84c448c3e5666/t/644e9853ecbee4661be67703/1682872403998/Butler_Ultra_Light.otf); } @font-face { font-family: TrendScript; src: url(https://static1.squarespace.com/static/63acfcc394c84c448c3e5666/t/644e9136ba9bd749c972a84f/1682870582458/TrendEffectScript.otf); } //Blog Fonts .blog-item-title h1.entry-title { font-family: 'Butler' !important; } .blog-title { font-family: 'Butler' !important; } .blog-more-link { font-family: 'Butler' !important; } //Heading 1 Font h1 { font-family: 'Butler'; text-transform: uppercase; } //Heading 2 Font h2 { font-family: 'Butler'; } //Heading 3 Font h3 { font-family: 'TrendScript'; } //Heading 4 Font h4 { font-family: 'Butler'; } //Text for Archive .archive-group-name-link { font-family: Butler; src: url(https://static1.squarespace.com/static/63acfcc394c84c448c3e5666/t/644e9853ecbee4661be67703/1682872403998/Butler_Ultra_Light.otf); } .archive-group-name-link {font-size: 40px; font-weight: bolder} /* Show comment box */ .squarespace-comments .new-comment-area.anon-comments-off.logged-in-commenting-unsupported { display: block; } Have tried multiple variations of this and not getting a solution. Did something on the backend change? Link to comment
Solution zsawtelle1 Posted August 2 Solution Share Posted August 2 It would appear that Squarespace updated something on the backend of the source coding for their sites that is now throwing a significant amount of errors for people using css & custom code, the custom fonts seem to be the most popular thing people are noticing at the minute. Not 100% how damaging the update was but it looks like most of the coding just needs an !important tag to override and being displaying the custom font again. Add !important to your text tags like the following h2 { font-family: 'Butler' !important; } that should solve the problem for now theverbalthing and Tiny_Coast 2 Link to comment
zk379 Posted August 2 Author Share Posted August 2 3 minutes ago, zsawtelle1 said: It would appear that Squarespace updated something on the backend of the source coding for their sites that is now throwing a significant amount of errors for people using css & custom code, the custom fonts seem to be the most popular thing people are noticing at the minute. Not 100% how damaging the update was but it looks like most of the coding just needs an !important tag to override and being displaying the custom font again. Add !important to your text tags like the following h2 { font-family: 'Butler' !important; } that should solve the problem for now Thanks, that did work. I had tried the !important; tag prior, but was separated by a ";" which probably caused that to not fix it. Looks like it is working again. Thank you for the help! zsawtelle1 1 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment