I ran into this issue on a new implementation. There is value in keeping your instance "clean"; i.e. removing artifacts of trial-and-error or just plain mistakes. To this end, I was able to easily remove the unwanted Knowledge Templates doing the following:
- Note the template tables being used by the unwanted templates. Check if they are unused by any other template. ("Template table" in the "kb_article_template" records.
- Add new "delete" ACLs to the "kb_article_template" and "kb_article_template_definition" tables. Versions of these already exist with "nobody" as the required role. I created new ACLs and gave it to the "admin" role.
- Delete the undesired records from the "kb_article_template" and "kb_article_template_definition" tables.
- Delete the tables noted in step 1 (listed in the sys_db_object table).
It's as simple as this. A few notes:
- You need the admin and security_admin roles to do this (and elevate to security_admin for the ACL work).
- Adding a new ACL with permissions to do what you want overrides the out-of-box ACLs, without needing to touch the latter (staying "out of the box"). (Your permission is granted by the "most permissive" ACL.)
- Of course when you're done with this, delete or deactivate the ACLs you created. I added a description to each like "Temporary delete access control on kb_article_template. Only activate if you need to delete a template rather than inactivate it.", and deactivated the ACLs when I was done. (Now we're back to out of the box for all intents and purposes.)
