In FontBase v2.21.0, when fonts in a collection are deleted (context menu > delete from disk), the font reference is not deleted from the collection. The font will not be visible in the collection anymore, but the font counter of the collection does not change. At least in time, collection information is not accurate.
Hello @PB-CCC, thank you for your post 
Indeed collections remember the fonts they contain if these fonts are removed from FontBase. This is by design so that if the fonts are accidentally deleted or removed and then re-added they will show up again in the collection that contained them without the need to remember which collection contained which font:)
Thank you again,
Yuriy
FontBase Dev Team
Please read my report again and change it back to a bug report.
If a design decision is based on the case of an exception, I may not agree, but that’s fine. But the number of fonts FontBase shows is wrong after deleting a font from a collection. And that’s a bug. So, this is a bug report, not a question.
Understood, changed it back, thank you for the clarification
This topic is also mentioned in incorrect number of fonts in collection shown
In reply to
Just to clarify, I completely understand your point and see how it makes total sense
Although I am not among the majority you’ve mentioned in your question and don’t feel it’s applicable to myself, you’ve mentioned a very interesting idea.
What does everyone here think about adding a context menu option (currently containing Activate/Deactivate, Package, Delete) to “remove old” or “remove obsolete” option, or “update”, which would remove the fonts from a collection which are currently not present in the app?
One of the concerns with making this process automatic is that a considerable part of FontBase users use network drives (NAS, GDrive, Dropbox etc) to store fonts, and in case of the connection breaking or something happening to the network even for a short duration the situation would be virtually indistinguishable from the fonts being deleted from a hard drive. As a result, when the connection is restored, the Folders in FontBase will update, but the Collections will have lost these fonts forever, potentially wasting many hours of sorting sometimes thousands of fonts. We used to receive a great deal of reports about this happening in the past, hence the introduction of the “collection memory” feature if you will. Basically separating the removal of fonts from a collection and the removal of fonts from FontBase font tracking. As @PB-CCC mentioned in the initial post, the issue arose when removing fonts from the hard drive, not removing fonts from a collection by dragging and dropping them in the Bin are on the right side of the app window.
Thank you again,
Thank you yuriy, for the clarification and explaining the working of this relevant part of FontBase. I now understand why this was the chosen solution for collections.
I hope I’m not asking a useless question: would it be possible to ‘mark’ a font deleted by user input?
If it isn’t possible to automatically differentiate user input (delete key) from e.g. a network connection break, then your suggested “remove obsolete” context menu item would be welcome imo.
1 Like
Hello @PB-CCC, thank you for the quick reply
No useless questions here:) If by “mark” you mean differentiate between font deletion from hard drive intentionally and temporary loss of access due to network issues or local hard drive unavailability, then I’m afraid the answer is no as far I know 
Thank you again,
might i suggest this:
if a font (local or remote) is deleted from a collection, its number should be removed.
if a remote font is not available because the server cannot be reached, the number could be red in color but still be counted.
the remote fonts from the unreachable server could still be listed since they will be needed when the server becomes available again, and the name could also be red to show its missing.
1 Like
I wanted to note here that the “collection memory” feature only remembers the font’s file name, so if you delete a font from a collection, then add a different font with the same name as the old file, it will not make the number in the collections any different; because it thinks it’s the same font even if it’s from another vendor/foundry.
1 Like