Captain's Log, Stardate 2025.248: Our engineering team has been hard at work in the dilithium mines (AKA debugging code) to bring you these important fixes. Live long and prosper!
Engineering reports
⛓️💥 Broken link checker ep. 1: The missing links mystery
Issue: Some genuinely broken links were pulling a Romulan cloaking device. They were there, they were broken, but they weren't showing up in the broken link checker reports.
Fix: We've disabled the cloaking device! All broken links, whether they're relative paths or full URLs, will now properly appear in your broken link checker reports. No more invisible broken links lurking in your knowledge base!
"Fascinating. The broken links were there all along, we just couldn't detect them."
⛓️💥 ⛓️💥Broken link checker ep. 2: The case of the false positives
Issue: Our broken link checker was suffering from some serious sensor malfunctions—it kept flagging perfectly good relative hyperlinks as "broken" when they were actually working fine.
Fix: We've recalibrated our sensors! Now the broken link checker will only report links that are actually broken, not every relative link it encounters. No more crying wolf about /home/your-awesome-article links.
"I'm a link checker, not a false alarm generator!"
🎨 Custom CSS: Make it so (much easier)
Issue: Updating color palettes in Custom CSS used to be quite the chore, because you had to hunt through CSS files to find every hard-coded color and replace them one by one.
Fix: We've implemented CSS variables at the top of our Custom CSS. Now you can update the color variables at the top instead of searching and replacing throughout the entire stylesheet.
"Engage! ...the much easier theme customization process."
🔎 Search results: Display titles lost in space
Issue: When searching for glossary terms, our search results were showing the internal term name instead of the display title.
Fix: Search results now show the display title (when one exists).
"The needs of the many (customers) outweigh the needs of the few (internal term names)."
💵 Billing page: The apostrophe incident
Issue: Customers with apostrophes in their last names (like O'Brien or D'Arcy) were encountering a white screen of doom when trying to access their FastSpring billing page.
Fix: We've made peace with apostrophes! Customers with names like D'Angelo can now access their billing information without encountering any errors.
"There are always... possibilities, including having an apostrophe in your surname and still accessing billing."
As always, if you encounter any issues that seem to defy the laws of physics (or just basic software functionality), please don't hesitate to contact us. We're standing by on all frequencies!
🖖 Live long and prosper
