Fonts are not groups anymore

Bugs
1

Please include the flowing when reporting a bug:

MacOS Sequoia 15.2
FontBase 02.21.0
The fonts are not included in groups anymore, approximatley all fonts now are individual fonts which may cause a hassle especially when fonts are more than 6 weights per family.
P.S.

I restarted the computer, fontbase, deleted the fontbase root file and also the ‘group fonts into families’ option more than once and the issue still persistent.

SCR-20241220-trdp
SCR-20241220-trdp2600×1738 390 KB

2

Hello @mhdhssamco, thank you for your post and welcome to the forum :pray:
A few questions, if I may, to better understand why this could be happening:

  1. When did this start occurring? Would you happen to remember any actions or changes right before this began?
  2. Does this also happen to the pre-loaded Google fonts?

Thank you again,

3

I am having the same issue—in fact I have never been able to get them to display in groups. Currently on Mac OS 15.1.1, FontBase 2.21.0

4

Hello, Thank you for your interest.

– I guess after the latest fontbase update. I did exactly nothing just that’s what happend.

– Nope, Google fonts are perfectly sorted and grouped.

5

Thank you for the quick reply and the additional information @mhdhssamco :pray:
This is quite strange, the latest update did not bring any changes to the grouping logic as far as I’m aware :thinking:
To understand if the cause is somewhere within the application or in the fonts themselves, would it be possible for you to do the following:

  1. Activate 5-10 groups of Google fonts in FontBase to download them the the Root folder.
  2. Deactivate the above fonts.
  3. Go to FontBase Root folder, copy these fonts into a separate folder outside of the FontBase Root folder.
  4. Add this newly created folder into FontBase as a watched or regular folder, as you would with any other font folder.
  5. Make sure “Group fonts into families” is turned on and check if the fonts in the newly added folder are grouped in FontBase
    ?
6

Hello @ida, thank you for your post and welcome to the forum :pray:
This shouldn’t happen normally if the data inside the font files is coded correctly, we’ll try to get to the bottom of this.
Same question if I may - are the pre-loaded Google fonts grouped when you view them in FontBase?

7

Configuration for testing:
VirtualBox + Windows 10 Pro (fully updated) + FontBase

Tested versions of FontBase:
2.20.7
2.21.0

Font families (pcs.):
Adobe Arno Pro (32)
Adobe Minion Pro (64)
Adobe Myriad Pro (40)
IBM Plex (16)
Public Sans (18)

When adding the above font families to the program:
Version 2.20.7 creates 5 font families in the program.

Version 2.21.0 creates:
12 families for Adobe Arno Pro
26 families for Adobe Minion Pro
12 families for Adobe Myriad Pro
7 families for IBM Plex
8 families for Public Sans

An album of screen shots on Imgur:
https://imgur.com/a/iBiJFNm

Addition: if you update the program to the latest version, then fonts added in previous versions of the program - are grouped correctly, and fonts added in version 2.21.0 are grouped incorrectly.

1 Like
8

Amazing research @NyBumBum, thank you so much :heart:

9

@yuriy , I replaced parser.js v.2.21.0 with parser.js v.2.20.7 in the current version of FontBase and now all newly added fonts are grouped correctly.

1 Like
10

I’ve had the same issue when setting up a new mac and added my whole FontBase library. The following workaround helped:

  • remove all fonts
  • downgrad to 2.20.7
  • re-add all fonts
  • update to 2.21.0
1 Like
11

I’m having the same issue on my home system. It was a fresh install in December 2024, with the latest 2.21.0 Fontbase. Fonts are listed as different groups even if they belong in the same family, the same way it’s in the original post. At work I have Fontbase 2.20.7 I believe (or if not, it’s older than 2.21.0) and all fonts appear correctly grouped. I have identical font collection on both systems. Google Fonts are correctly grouped on both PCs however, so t he issue only seems to exist with local files

I did backup and restore a few files in order to keep my collections of fonts within Fontbase across the older Windows install to the new one. No idea if that could be a problem here. Those files are everything inside: %appdata%\FontBase\IndexedDB

Windows 11 Pro 24H2 build 26100.2894
FontBase 2.21.0

1 Like