Changes in Version 2.3.1

New Features

• FontExplorer X Pro now recognizes FontAgent Pro 4.1 when checking for monitored applications

New Server Features

• Improvements when redrawing the User Interface when connected to a FontExplorer X Server with many fonts
• Performance enhancements when logging on/off to/from a FontExplorer X Server
• Performance enhancements for FontExplorer X Servers with large amounts of folders/sets

Fixed Bugs
Client only:

• The initial font import during setup occasionally resulted in a crash
• A crash occurred when accessing a corrupt database file
• Sometimes the application crashed during start when a nested folder structure on the disk had changed
• Delete missing fonts (fonts showing up in red) from the client did not refresh local set/font counts
• FontExplorer X Pro crashed at start when the application home directory was set to READ ONLY
• FontExplorer X Pro crashed at start when a network directory was chosen for initial font import during setup
• Server Admin Manual was not available on www.fontexplorerx.com

Server Administration:

• The default Offline Usage status was not displayed correctly in Options
• When disconnected, Hide Local was not working when inherited from Options
• Renaming a server set from the server set Properties contextual menu didn't update the source tree
• Removing a font from a server set deleted it from the server Fonts library
• Occasionally a "System.OutOfMemoryException" occurred when importing huge font sets into the server
• On server font activation, sometimes every folder/set checkbox was highlighted after a Reload Sources
• The Restore backup function on the server didn't work in some situations
• A server backup sometimes couldn't be created using the Create Backup button due to a failure on the server side
• The user interface occasionally was not refreshed after nesting existing server folders. This did not occur with new server folders
• Fonts dragged into existing server sets were sometimes not copied (counter was not incremented and no font showed up in list)
• When a server set was renamed from the Properties contextual menu and then renamed via Rt Click>Rename, an invalid name was shown
• In certain situations, a Power User couldn't access the Properties menu on server sets/folders ("No Permission" error)
• Recently deleted server sets/folders appeared in Offline mode
• When a font had been deleted on the server using Remove Set and Contained Fonts, it couldn't be uploaded again
• TTC server fonts were not displayed correctly when imported into the server via the PC client
• Server folders could not be renamed after adding sets ("No Need to Move Source" message displayed)
• Server library counter showed wrong font count after server restore
• A font was not removed from server library until the next login (or Reload Sources operation), when a user with Write permissions had removed a font from a server set
• Font counter showed 0 after uploading fonts in a new server set via a second client (Mac or Win) while a user was logged in. This remained across logins and subsequent Reload Sources
• A crash occurred when reimporting a font to the server library after Remove Set and Contained Fonts, where the font had been included
• Server set counter showed incorrect font counter after Drag&Drop import of a huge amount of fonts
• While logged in under a standard User Account, the font counters were reset to 0 when selecting Reload Sources
• Removing a font from a server set occasionally resulted in a crash
• Sometimes the client crashed when importing a font to an existing server set
• When the server was stopped during account creation and Save was pressed in this situation, an exception occurred. Re-login was not possible until client was restarted ("No Permission" error)
• "No Permission" error was shown at server re-login, when a client had been restarted and tried to login to the server which was restarted (Offline Mode enabled previously)

Known issues

• System-Wide Font Requests are not supported at the moment
• On a multi-user machine (one machine with separate login accounts) FontExplorer X Pro can only be launched by one user. If another user attempts to launch FontExplorer X Pro a message will be displayed: "FontExplorer X Pro is already running in another user session"
• Manually activated PostScript fonts do not display in Adobe applications when font activation is temporary. Workaround: select Activate fonts permanently (required when using Adobe applications) in Options/Advanced panel or activate fonts via the plug-in font request dialog
• The auto-activation setting will not be effective for the Quark XPress Plug-Ins. When opening a Quark XPress document, the plug-in dialog will always open. If all the fonts are available in FontExplorer X Pro simply click on Activate All
• Smart Sets do not work correctly when placed in Folders
• It is not possible to remove newly imported fonts from a server set without logging back on to the server
• Dragging and dropping a server folder onto itself may cause a server crash

Adobe Creative Suite applications:

• When using Adobe Creative Suite (2,3,4 & 5) products to create new documents, Postscript server fonts that are activated on the server are not displayed in the Font dropdown menu. Postscript fonts in an existing CS document that are activated on a server, will behave properly; the fonts will appear in the Font dropdown menu and can be activated/deactivated appropriately. This issue only applies to PS server fonts, all other font types (TrueType, OpenType) work correctly. The work around is for the customer to update their PS server font to one of these other font formats. Local Postscript fonts will behave properly in Adobe Creative Suite products

Adobe InDesign:

• When a font contained in a very long set name is displayed in the plug-in request dialog, the set information is cropped