Disclaimer: Not sure if I'm misunderstanding functionality or not.

Drupal: 6.11

I added a few Knowledge Base attributes --
Key=> BI, Value=> Business Intelligence tools, Key=> Cognos, Value=> -- Cognos BI
Key=> CMS, Value=> Content Management Systems, Key=> Drupal, Value=> -- Drupal

Domain is still Knowledge Base system, parent domain is still "-" (root).

I created a KB entry for Drupal.

If you go to Attributes and filter on Knowledge Base System, I then arranged the new entries to the correct display order.

I then click on Knowledge Base, and it defaults to the topmost entry -- Business Intelligence tools.

First issue: there's apparently no global way to pull a master list of all major KB topics.

I explicitly selected the "-- Drupal" category.

Nothing listed.

There ~should~ be an entry; I can see it under admin/content, and the type reads as "Knowledge Base"...so did I break things, or is there an issue here...?

Comments

GreyHawk’s picture

GreyHawk commented

Dang -- sorry; didn't mean for "First" to be highlighted like that.. got pulled away as I was trying to figure out how to best present my issues/questions, and forgot to go back. :( Now, I simply look like (more of?) an ...well, sorry. Anywho -- loving the Storm module so far, and hoping/suspecting that one of the higher revs in Dev or the repository might already have the KB issue (if it ~is~ an issue) already addressed.

GreyHawk’s picture

GreyHawk commented

Storm Demo appears to exhibit similar behavior -- which is weird, as it appears to have three KB articles already.

I added one, but not to the default topic (Operating systems), and it doesn't show.

Magnity’s picture

Magnity commented
Title: Knowledge Base -- Notes and issues (?) » Knowledge Base doesn't allow filtering by non-default attribute
Category: support » bug

Bug confirmed + changed title slightly to make the issue more specific.

GreyHawk’s picture

GreyHawk commented

Thanks, Magnity.

I think the Storm project shows a lot of promise, and would like to help by testing and documenting.

I'm not a PHP or CSS whiz, but will be learning both as well as becoming more familiar with Drupal, so if I get to a point where I can help out with any actual development I'll toss my hat into that ring, too.

*Edited to add -- a default "all entries" filter would be useful to list all KB entries, too.

Magnity’s picture

Magnity commented

Testing and documenting is a massive part of development so its great to hear that you're on board. I'd encourage anyone else as well to get involved in this or any other way. This will really accelerate development.

A great way to help with testing is to run a copy of the -dev version as well - with a caveat that the -dev version may contain more bugs so think about the data that you are using it for. However, the more that can be ironed out in -dev, the better the stable versions are when they are released.

Magnity’s picture

Magnity commented
Status: Active » Fixed

Should now be fixed in -dev.

http://drupal.org/cvs?commit=208506

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.