Knowledge Base articules lacking documentation

[Nader]

As we all know that Knowledge base articles are an invaluable source for information and trouble shooting issues with Graphisoft applications, there is no doubt in that.

But lately I have been facing a lot of issues that can not be solved by following the indications mentioned in the Knowledge base article (I see it as normal and expected), because sometimes the used platform is simply different, for example when the log in page is missing when using LMT, and for that specific case the article has made a very good job to explain how to trouble shoot it for a PC, but the platform I was interested in was a mac !!!!

But the reason, I have opened this thread is to ask, if these articles are all closed to comments, how can we deliver those missing parts in the articles ????

[Noemi Balogh · Accepted solution]

Hi Nader,

We closed commenting because people often shared data there that shouldn't be shared in such a way. (For example, we received cmdust logs copy-pasted in a comment... apart from the fact that it can contain sensitive data, the user will probably receive no help for such issues there, as these are individual cases that should be handled via technical support.)

We'd like to implement something easy and straight forward to collect feedback about articles, and we have some things in mind already, but we need to work them out. Right now, the best I can recommend for this is sending an email to community-support@graphisoft.com with the link to the article and a description of what's wrong or outdated in the article. 

Thank you for your attention to the articles and their quality.

Kind regards,
Noémi