As the old saying goes, when life hands you lemons, make lemonade. And when life hands you software bugs, make your product better. (I know...it just doesn't have the same delightful ring to it.)
In the last week, we've released these changes in KnowledgeOwl:
- Glossary term imports used to fail silently when they encountered a character they couldn't process. We've updated this workflow so it includes a warning message to let you know the import didn't succeed and which lines in the CSV file caused errors. You can see a screenshot of the error message--as well as recommended troubleshooting steps--in Troubleshooting glossary term imports.
- For knowledge bases with Default Access set to public, but containing some restricted content: if a reader tries to access a restricted article, we have historically just sent them to the No Access page. We now include a parameter in the URL to track what page they were trying to go to, which makes it possible to add a script to send them to the Login page instead of the No Access page. Contact usif you'd like us to add that script to your knowledge base!
- For knowledge bases using any of our standard Google fonts, like Open Sans: we noticed that if you set your default font for Headers or Article Text to be Bold weight in Settings > Style, the bold was not consistently applied everywhere. We've updated the settings for these Google fonts so that they should properly apply bold (and light weight, where available) to:
- Article text in the live knowledge base
- The display of text in the article editor
- Individual article PDFs: you'll need to save an article with changes to see the difference; we can regenerate them all for you, too!
- Custom PDFs: you'll need to regenerate them to see the font weight difference
- Standard PDF: you'll need to regenerate this to see the font weight difference
