Will topics created by non-admin users will be added to the KB? I want to use the KB to upload curated content from many categories, but would like to make sure that topic generated by non-admins will not be added to KB. Please confirm — thanks in advance!
if one choose a category as a knowledge base, and then he removes it from being knowledge base, both by selecting/de-selecting the option in category setting, the category is not removed from knowledge base!
I’ve been dealing with the same bug, I’ve also sent a bug-report.
Also, maybe I’m being a bit of an idiot (I’ve been known to do that at times), but if I nominate a category and a sub-category within it to be knowledge bases, the subcategory’s base topics are duplicated within the category’s base. I understand that behaviour within a forum, but is there a way to cull the duplicates within the knowledge base? Especially as the duplicated topic leads to an error instead of the post in question when clicked.
Just an idea: There is a functionality that this plugin could “steal” from another similar one ( Knowledge Explorer Plugin ). It’s the ability to select what’s displayed in the knowledge base with tags instead of just categories. That enables to just cherry pick some topics from anywhere.
@Nacho_Caballero You could have it always expanded if you force expanded to be true in the knowledge-base-nav component, and remove the bound events in that component. I don’t have the time right now to work that up for you, but happy to accept a PR / give further pointers.
Justin has gone even further now and created the Knowledge Explorer Plugin. I’m not sure how it relates to the theme component he created and its status… but I think it goes further. I agree with you Angus that it might be better to focus energies on helping Justin. Using official plugins is always a Good Thing™.
That said, there are quite a few features I really like from this knowledge base plugin that I miss! We put some excellent thought and work in, Angus, so let’s think some more about it before we throw it all away. If Justin is not interested in them and if we have a maintainer, maybe we should keep going here. Also, our plugin is actually working pretty well now and Justin’s work is still in progress and there is not much info available on his plans.
I think Justin is pursuing a different model where sites have maybe one or two KB categories with lots of topics that can be drilled down into using tags. Topics inside them appear as discussion topics with all the replies and discussion features intact. Ours is based on having one category with lots of sub-categories that can be drilled down into using a navigation menu. Topics inside are clean and have no discussion features, with link across to the discussion topic.
In bullet points, features I like are:
automatic support for sub-categories so you can have a kb category, and each sub-category is automagically included as a section. lovely!
respects category permissions to display categories and topics within them only to people with access
super handy table of contents that can have sections opened/closed to drill down
ability to manually set the sort order of topics in the table of contents
landing page text for the kb
landing pages for each section drawn from the about page
clean display of the kb topic, with no discussion features (but with link across to the discussion)
Some work that seems needed to bring this plugin up to speed:
toggle to switch back and forth between kb view of topic and discussion view, that works both ways (feature request)
ability to restrict keyword search kb topics when within the kb
ability to link directly to a section to display it without the distraction of other sections (eg /k/helpdesk to display just the helpdesk knowledgebase). Maybe also ability to confiure multiple knowledge base root categories.
ability to edit kb topics directly from the kb, maybe by adding EDIT link next to PRINT
Some bugs I noticed trying it today on my work community:
name space collision with knowledge base theme component (I think - this may be resolved)
printing works, but takes user away from page and displays topic with pencil shaded theme. (on my site, also does not exclude some theme customizations that interfere)
KNOWLEDGE BASE is displayed on top menu, but links to /c/kb/l/kb path which is incorrect. Should link to /k which does work.
for some reason, first item on the knowledge base menu is knowledge base - and seems to contain all topics in the sub-categories. links broken.
It seems this plugin causes my discourse instance to fail (bootstraps, but site doesn’t load) if I use it along with the Solved plugin. In other words, I seem to have to choose between the two plugins. Wondering if anyone else has run into this?
edit: Specifically it seems to fail in this manner if I try to nav from the admin panel to the homepage/forum index:
while trying to load [/categories.json](DOMAIN/categories.json)
with domain being my app’s root domain
edit: This looks to manifest the same way as the bug @Ryan_Hyer is mentioning. Again (same logged error), it stops if I remove the solved plugin (which is listed in his list of used plugins) so I assume it is some sort of conflict between the two
Yeah the idea on Knowledge Explorer is to filter and search any knowledge-base type topic across a set of selected categories and tags. It’s more about discovery and less about creating a structured KB like this plugin does. There are definitely two different use cases here.
The iteration released 2019-10-31T05:00:00Z pulls just the OP into the explorer view, versus the discussion. There is a link to the discussion if that is needed however.
Given the issues with this plugin, I would not recommend installing it until a path forward has been determined for it by @angus and his pavilion colleagues. The Knowledge Explorer Plugin is an impressive alternative, showing much promise. It will likely be an official plugin so it’s highly recommended.
Cool! I can repro this. Let’s keep the convo about this bug over here: