- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Navigation breaks when adding CSS Key custom fonts
Hi there!
I'm trying to add custom fonts to the Brisk 2 Weebly template and I am running into an issue. When I add the CSS Key under the <head> tag on the two header types, the left hand navigation breaks. The sub-pages don't show up. I'm not understand why this is happening. I've done this process with several other templates and all seemed to work fine.
After I add the CSS Key and replace the Font-Family declaration blocks in the styles tabs, the custom font will work, but the navigation doesn't. I figured out that the nav breaks with just the first step.
Any help would be much appreicated. Thanks so much!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report

- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Hi @tjpom Can you please post a link to the site you are referring to? Thanks!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report
- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Thanks for your response @Bernadette
I've done some further testing since my first post. It turns our that the issue is not related to the additional CSS reference I was adding to header.html. The issue occurs when I simply save a second version of the theme, even without any modifications to an object (html, less ect).
Here are the steps I've taken to recreate the issue (multiple times):
Create a new site.
Choose the Brisk 2 theme.
The Brisk 2 theme has 5 default menu items (home, shop, about, journal and contact).
Add a sub-page named "First Subpage" to the "about" page.
Publish the site. You can access it at https://itsjustatest12.weebly.com/
Confirm that the sub-page is accessible in the menu.
Make a copy of the site.
Go to edit the new site.
Navigate to Theme> EDIT HTML/CSS
Click the "Save" button and name the new version of the theme "testTheme." Note that no modifications are made to any html or less object.
Confirmed that the sub-page is no longer accessible in the menu.
Publish the site. You can access it at https://itsjustatest14.weebly.com/
I've also repeated these steps in a completely separate Weebly account and the issue does not occur in that account.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report

- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Interesting that just making it a custom theme would do that. Is the custom font something you need to upload files for, or is it a Google font where the font resources are hosted by Google. It's possible to do this without editing the theme, though it's a little easier with Google fonts.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report
- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
The web font I'm using is subscripiton-based and it's offered by Hoefler & Co (typography.com). I've successfully embedded the code and displayed the font in other Weebly Themes.
I'm still wondering why the issue is occurring regardless of any change to the code.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report

- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
I'm not sure why this is happening since it shouldn't really change anything just by saving a theme as a custom theme. I don't know how the code works that does that, though. You could try adding your CSS and other HTML tags to the Header Code field for the site. Rather than directly editing specific CSS rules to use the new font, you could also override them there.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report
- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
@Bernadette and @Adam how do I get this issue escalated in the Weebly's technical support chain? It appears to be a bug in Weebly's backend code. I have two accounts, one created awhile ago and one more recently. Applying the same steps outlined previously in this forum thread, the older account does not have the issue but the newer one does. I've exported and downloaded the theme from each account and have run a comparison check on all files. They are identical. There's nothing in the code that I have access to that can cause or correct the issue.
Weebly support please help!
Example from older account
https://itsjustatest13.weebly.com
Example from newer account
https://itsjustatest14.weebly.com
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report

- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Was it only Brisk 2 that did this, or does this happen if you switch to a different theme and save it as custom?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report
- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
@Adam That I'm aware of, it only occurs in Brisk 2 when the Nav Position is set to sidebar. When it's set to Top Left or Top Right the sub pages are accessible in the navigation. I want to use Brisk 2 because it offers a sidebar navigation.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report

- Subscribe to RSS Feed
- Mark Thread as New
- Mark Thread as Read
- Float this Thread for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Ok, I'll do some testing and take it to our engineers.