Non-GitHub-Integrated KB Articles still show GitHub Integration-related links on frontend

[raamdev]

When a KB Article is created inside WordPress (instead of using the GitHub Integration to create a GitHub issue and Markdown file), the KB Article still shows the links to "improve this article" (links to the associated GitHub Issue) and the "[edit]" link (which links to the associated Markdown file).

However, when a KB Article is created inside WordPress instead of using the GitHub Integration, there is no GitHub Issue or Markdown file associated with it, so both of these links lead nowhere useful (well, at least the "edit" link leads nowhere useful; you could argue that linking to the KB Article GitHub repo /issues/ is still somewhat useful, as someone could just create a new GitHub Issue to suggest improvements, but I'd say that's not the intended behavior here).

Both of these links should be removed when a KB Article is created inside WordPress instead of through the GitHub Integration.

Example: http://s2member.com/kb-article/can-i-customize-pro-forms/

---

What Actions Need To Occur Here?

• [x] Fix bug in this template file and in this template file that incorrectly link to the MD file on GitHub. Instead, this link should lead to the KB Article within WordPress, where the article can be edited within the WP Dashboard. When linking to the WordPress Dashboard instead of GitHub, the GitHub Icon should not appear.
• [x] The link that reads "how can we improve" should lead to the New Issue form in the underlying GitHub repo instead of the full list of Issues, which is a little confusing for an end-user.

[jaswrks]

Adding a list of actions (↑ above) that need to occur.

[raamdev]

Updating next action list to include the following note regarding the [edit] link: "When linking to the WordPress Dashboard instead of GitHub, the GitHub Icon should not appear."

[jaswrks]

Ah, thanks!

[jaswrks]

This has been resolved. s2Member.com and ZenCache.com updated.

[raamdev]

Tested and confirmed fixed. Thank you! :-)