Remove nhtml and ntools from a .bog

What it does

• Reads a .bog (zip, gzip or plain XML) or a .dist station backup.
• Resolves every module prefix properly, so it finds the components whatever they are called in your file — sbs:, sbsmi:, kvg: or anything else.
• Removes those components and everything under them.
• Removes links that pointed at what was deleted, so you are not left with broken links.
• Re-binds any module prefix that a deleted component happened to declare first.
• Leaves your HTML, CSS, JavaScript and px graphics completely alone.
• Writes a report listing every removed component, the files and pages it pointed at, and anything still naming the modules.

What it deliberately does not do

It does not edit query strings. If a BQL or NEQL filter somewhere in the station mentions ntools:SMSRecipient, that gets listed in the report and left where it is — rewriting somebody's query is not the same thing as deleting a component, and you should look at it yourself.

It does not touch graphics. Several ntools types are px widgets, which live in .px files rather than in the station database. Those cannot be fixed from the bog and will still need attention in Workbench. Feed it the whole .dist backup instead of just the bog and the report will tell you exactly which files to look at.

Why a station fails without these modules

A Niagara station stores each component's type as a module and type name. When the station is opened on a host where that module is not installed, Niagara cannot resolve the type. Depending on version and context you will see the component as unresolved or as a tombstone, get errors in the application director, or find that the station will not start at all. Removing the components is one way out of that. Installing the modules is the other.

Which modules