FAQ v6.0.9

Release Date: July 29, 2026 Tags: CORRECTNESS, CONTENT INTEGRITY, PRIVACY, AI, KNOWLEDGE BASE, KYC, ANALYTICS, THEMING

Overview

A full review of the FAQ addon — every screen, the AI helpers and both the public and admin sides.

The addon moves no money, so the things checked were different: a disabled article stays hidden, personal data stays with the admin, submitted content is safe, every admin screen is properly protected, and the numbers on screen match reality.

Much of it held up. The privacy boundaries in particular were already sound — a submitted question's name and email never reach a non-admin, and feedback is limited to one entry per person per article. What did not hold up was content integrity: text was being mangled as it was saved, and two shipped features could not produce a single result.

It also turned up three finished sections of the public FAQ page that had never been placed on it. Trending searches, browse-by-topic and most-viewed articles were all written, all working, and all unreachable — no visitor had ever seen any of them. They are on the page now.

It also repaints the addon. Every FAQ screen, public and admin, was painted in a fixed sky-blue palette that ignored whatever colours an operator had configured. The FAQ area now follows the platform's own theme, in both light and dark mode.

---

Upgrade Notes

No changes are needed for existing installs. Everything in this release applies as soon as you update.

---

Added

Three finished sections had never been placed on the page

The public FAQ page now shows three blocks between the search box and the category tabs.

• What Others Are Searching: the queries other visitors have actually run, each with how many times it has been searched. Clicking one runs that search immediately.
• Browse by Topic: a card per category, showing how many articles it holds and how many times they have been read. Clicking a card scrolls down to the article list and switches it to that topic.
• Most Viewed: a ranked list of the most-read articles, each with its view count and how many readers marked it helpful.

All three were built and working, but none of them had ever been placed on the page, so no visitor had seen any of them. The trending block is the one the search fix below refills — it had nowhere to appear even once there was data to put in it.

---

Changed

Every FAQ screen now uses your platform's colours

The FAQ addon was painted in a fixed sky-blue and purple palette — gradients, glows and heavy shadows that looked the same on every install no matter what an operator had configured. All of it now follows the platform's own theme: the FAQ page and article page, the troubleshooter, and all five knowledge-base admin screens, down to the drifting orbs and particles behind the analytics header and the colours of the category breakdown chart.

• Applies to an operator who has set a custom primary colour will see the FAQ area pick it up after updating.

---

Fixed

Content was mangled when saved

Text was being converted into web codes before it was stored, so the codes — not the words — were what visitors saw.

• Typing "What's the fee for a BTC/USDT withdrawal?" stored — and showed every visitor — What's the fee for a BTC/USDT withdrawal?.
• It got worse on every save, adding another layer of codes each time. The "Move FAQs" action re-saves every FAQ on a page, so one click degraded a whole page of content.
• The same thing happened to the FAQ image, so every newly created FAQ showed a broken image. Editing the FAQ accidentally repaired it, which is why the problem went unnoticed for so long: anyone who tested by editing never saw it.
• Feedback comments were mangled the same way, permanently — which also broke the admin's search over them.

Text is now stored exactly as it was typed, and images are checked properly instead of being mangled.

Two features could not produce a result

Search analytics had recorded nothing for seven months. Every search made by a visitor was silently discarded.

That emptied the "trending searches" section on the public page and the admin's top-searches widget, but the real loss was the list of searches that found nothing. That is the single most useful thing this addon can tell an operator — it is the list of questions your knowledge base does not answer — and it had been blank since December.

Every search is now recorded, signed in or not. Who searched is deliberately not recorded: what this report exists to answer is what are people asking, which needs no identity.

Answering a submitted question notified nobody. The answer was saved and nothing else happened — while the public form told the asker "We'll send you an email when we have an answer for you" and the admin screen confirmed "Answer Sent." Neither was true. There was no email, no notification, and no page anywhere in the product where the asker could read the answer. Both sides believed the exchange had completed.

Answering now emails the address the question was submitted with, and raises an in-app notification when that address belongs to a registered account.

Unpublishing did not hide anything

Disabled articles were correctly hidden from the FAQ list, but anyone who had the direct link could still read them in full. Unpublishing is how an admin retracts something wrong or no longer meant to be public, so it has to hold everywhere — it now does.

Records became permanently unreachable

Submitted questions. The admin list only ever loaded the newest hundred questions, and the tabs and search box worked over just those. Past a hundred questions, the oldest still-pending ones fell off the end: gone from the Pending tab, invisible to search, and reachable by no link. Those people's questions could never be answered. The list is now paged and filterable, and the tab counts cover every question rather than the ones on screen.

Editing an FAQ. The edit screen only looked at the first ten FAQs, so opening any FAQ that was not on page one reported "FAQ not found". Any FAQ can now be opened.

The troubleshooter narrowed the whole knowledge base down to matching articles, but only ever considered ten of them, so on any real install it was answering from a fraction of the content.

The AI helpers had no cost ceiling

All five AI features passed whatever was typed straight to the paid AI service with no size limit, so a single oversized request could run up a real bill, repeatable as fast as the network allowed. Each field now has a sensible limit — a topic is a sentence, an answer is a few paragraphs — and an oversized request is refused before anything is sent.

The editor's AI buttons invented content

The four "improve with AI" controls in the FAQ editor never called the AI service at all. They were canned text behind a two-second fake spinner — and not harmless placeholder copy: on a question mentioning payment, "Improve Answer" produced a complete payment policy stating that the platform accepts American Express, Discover, PayPal, Apple Pay and Google Pay, offers bank transfers over $500 and invoicing for bulk orders, and published a support phone number of 1-800-123-4567. An admin who clicked Improve and then Apply published that as official policy on a crypto trading platform.

The improve and tag buttons now use the real AI service, and say so honestly when it returns nothing.

Submitting a question ignored the verification requirement

When asking a question was placed behind a KYC verification level, hiding the form was the only thing stopping anyone from using it. The form disappeared for an unverified visitor, but a question submitted directly — without going through the page — was accepted and queued for an admin like any other.

• Fixed the server now applies the same verification requirement itself and refuses the submission, naming the level required. The notice shown in place of the form names that level too, instead of a generic message, and no longer flashes on screen for a moment before the check finishes.
• Applies to installs that have this feature gated. Where it is not gated, nothing changes.

Smaller corrections

• The feedback confirmation showed raw placeholder text. After voting on an article or leaving a comment, the confirmation read thank_you_for_your_feedback instead of "Thank you for your feedback!" — on the article page and under every item on the FAQ list, in every language. It now shows the real sentence, translated.
• Analytics trend lines label each point with its date. Hovering the small trend lines on the Views, Positive and Negative cards used to show a bare number with nothing to say which day it belonged to. Each point now carries its date, following the Weekly / Monthly / Yearly period selected at the top of the page.
• Batch AI Enhancement uses the standard admin dropdown. The "select an FAQ to improve" and "select a page" pickers were plain browser drop-downs, so a long question stretched the control out of shape. Both are now the same dropdown used everywhere else in the admin, with long questions truncated.
• Every knowledge-base admin screen ended in a deep band of empty space. The FAQ admin area added its own bottom spacing on top of the spacing each screen already carries, so Overview, Manage, Questions, Feedback and Batch AI Enhancement all finished with 160 pixels of blank page below their content instead of the 64 used everywhere else in the admin. The extra band is gone, and the FAQ admin now ends exactly the way every other extension admin area does.
• Questions now sits above Feedback in the knowledge-base admin menu. Questions is an inbound queue somebody has to answer; Feedback is a signal you read afterwards, so the actionable one comes first. Anyone used to the old order will find those two entries swapped.
• Display order 0 meant "last". An admin who deliberately put an FAQ at the top of a page found it at the bottom. It now behaves as expected.
• FAQ sections showed every article on the platform. Per-page organisation is the organising idea of the whole admin surface, but the public side ignored it — so an FAQ section embedded on one page listed everything. It now shows only that page's FAQs.
• Tags and related articles behaved differently on different servers. They now behave identically everywhere.
• Deleting an FAQ left it listed as a related article on other FAQs forever. Invisible to readers, but it cluttered the editor and made the counts disagree. References are now cleaned up on delete.
• The public "recently answered" list took the five newest questions and then kept only the answered ones, so a burst of new questions emptied it. It now always shows five answered questions.