SOLVED: Font Manager: Favorites Issues

[datgausaigon]

Browser: Chrome 135.0.7049.115 (Official Build) (64-bit).
OS: Windows 11.

Can not “add to Favorites” with:

• Standard Fonts
• Google Fonts (Not downloaded)
• Adobe Fonts
• Only “add to Favorites” with “Custom Fonts” (Google Fonts downloaded)

After a Font “add to Favorites” can not browse and select another fonts.

[timmse]

Hi Gấu,
Thanks so much for your report!

I noticed this while replicating another issue and already added it to our bug tracker
Seems to have crept in over the last few meters, as it worked wonderfully in the previous tests.

Best regards,
timmse

[timmse]

Hi Gau,

We fixed this issue in Bricks 2.0 beta, which is now available in your account.
Changelog: Bricks 2.0-beta Changelog – Bricks

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

[datgausaigon]

Hi @timmse ,

Thanks for the bug fix.
Basically the bug has been fixed for the issue of displaying different Google Fonts but a new related bug has appeared.
Favorites and Custom Fonts (Google Fonts downloaded) will be in Favorites, meaning there are Fonts in Favorites and Custom Fonts will not have any Fonts.

Steps to reproduce the bug:
(If Download (Custom font) first, Issue will not occur)
Issue:

• Edit Page with Bricks / Settings / Font Manager
• Google Fonts → Select Inter → Add to favorites
• Google Fonts → Select Prata → Add to favorites
• Favorites → Select Inter → Download (Custom font)
• Favorites → Select Prata → Download (Custom font)
• Return to Builder interface → Add Header Element
• Go to Typography / Font family → We see Issue:
  – Favorities: 4 Fonts: 2 Inter, 2 Prata
  – Custom Fonts: 0 Fonts
• Save Page, go back to Header Element check again, Issue still have.

Adjust the display of Fonts in Favorites and Custom Fonts, we will see the display as follows:

• After the error Issue 1 occurs.
• Edit Page with Bricks / Settings / Font Manager
• Custom Fonts Select Inter → Remove from favorites
• Custom Fonts Select Prata → Remove from favorites
• Custom Fonts Select Inter → Add to favorites
• Custom Fonts Select Prata → Add to favorites
• Return to the Builder interface → Select Header Element
• Go to Typography / Font family → We see the display:
  – – Favorities: 2 Fonts: 1 Inter, 1 Prata
  – – Custom Fonts: 0 Fonts
  — Continue:
• Custom Fonts Select Inter → Remove from favorites
• Custom Fonts Select Prata → Remove from favorites
• Return to the Builder interface → Select Header Element
• Go to Typography / Font family → We see the display:
  – – Group Favorities not seen
  – – Custom Fonts: 2 Fonts: 1 Inter, 1 Prata

Screenshots:

Thanks

[Matej]

Hi,

thank you so much for the steps. I was able to replicate the issue, and I’ve created an internal bug report.

Best regards,
Matej

[datgausaigon]

Hi @timmse @Matej ,
Thanks so much guys.

[datgausaigon]

Hi @timmse @Matej ,

I found another related issue.

Fonts in “Google fonts” and “Custom fonts” (After Downloaded it from Google fonts into Custom fonts) can both be added to “Favorites”

Steps to see the issue:

• Google fonts → select Inter → Add to favorites, Download (Custom font)
• Custom Fonts → select Inter → Add to favorites
• Return to the Builder interface → Select Header Element
• Go to Typography / Font family → We see the display, 2 Inter fonts in Favorites

Thanks

[Matej]

Hi @datgausaigon,

even though it might look like a bug, it’s actually not. Once you download your Google Font, they are then two separate fonts - One local, one from Google.
You can then remove the Google Font from favourites, or you can rename the custom font.

Best regards,
Matej

[datgausaigon]

Hi @Matej ,
Thanks for your reply.

I reviewed it and got it as you said. This is not a bug, it is a Flow and UX issue. We can describe and clarify it in the documentation. Because “Custom fonts” and “Google fonts” are 2 different categories and can be added to “Favorites”.

Thanks

[timmse]

We’ve fixed this issue in Bricks 2.0, now available as a one-click update in your WordPress Dashboard.

Please take your time to read the changelog entry before updating: Bricks 2.0 Changelog – Bricks, and let us know if you continue to experience issues.