Hi @MarkAtTruth - It looks like our out of the box version of the component does have the author listed. This is a screenshot from my test environment: It shows users that have the BlogAuthor role for the Blog in question. On your community, it looks like you have a customized version of the component that comes from our services' Themes plugin. It behaves differently and shows the bio of the blog author (without the username) or the bio of any commenter if you click the permalink to their post. The latter of which seems like a bug to me, my expectation is the component should only display the bio for the author of the blog. This behavior was already reported internally and is under investigation, if you'd like to submit a ticket we can keep you updated on the status of that investigation.  If we can get that issue addressed, it should be a less confusing experience and adding the username to the component wouldn't be required. ... View more

@CarolineS - Thanks for your patience. I filed a bug for this, it looks like it only occurs in TKB v4. The TKB article dashboard link should only be displaying on Forums if the settings under Community Admin -> TKB -> " Knowledge Base for Forum Topics" are in use. In this case it's throwing an error because there is no TKB defined in those settings, which normally wouldn't cause an issue since that option shouldn't be displayed. I'll update the ticket now to reflect the above. ... View more

@CarolineS - Thanks for flagging this. I'll take a look at the issue and the ticket in question and circle back. In general, an expected behavior shouldn't be an exception error. If it was a permissions issue I would expect to see a permission denied error or better yet the option shouldn't display in the menu. I'll update here once I have more information. ... View more

@kgroneman - I had a look at the case, we were referring to the form I mentioned previously. While technically still true that multiple discussion styles share the form I'm not sure we need to do anything with it to do what you've described - as long as you're OK with the component being above or below the editor form. In this case, you'd just need to create a custom page to override the PostPage, e.g. PostPage.ideas, and set it at the Node level admin of the idea exchange you'd like to change. This is an example of what I mean from my test environment: For reference, the documentation on this lives here: https://community.khoros.com/t5/Pages-and-layouts/Override-a-default-page/ta-p/108961 Please let me know if that helps or if you have any questions. ... View more

No problem, glad that worked. I've got this scheduled to deploy during the maintenance window tomorrow evening. ... View more