// module reference
nhtml
Serves a responsive HTML5 navigation front end from a Niagara station. A single HTML5 service holds the nav structure and points at CSS/JS/nav files in the station file space.
Why the prefix is not always the same
A bog does not store the module name on every component. It stores a short prefix, and binds that prefix to a module once, like this:
<p n="HTML5Service" h="27b7" m="sbsmi=nhtml" t="sbsmi:HTML5">The prefix comes from the module's preferred symbol, which has changed
between builds — kvg and sbsmi have both been
used — and two modules that want the same symbol get told apart per file. So
searching a bog for the text nhtml will miss components, and
searching for a prefix will find the wrong ones. The binding has to be
resolved. That is what the tool on this site does.
Types in the station database
These are components that live in the station tree, so they are in the bog and the tool can remove them.
| Type | Seen in a bog as | What it is |
|---|---|---|
HTML5 |
kvg:HTML5 sbsmi:HTML5 |
The main service. Usually mounted at /Services/HTML5Service. |
EquipmentList |
kvg:EquipmentList sbsmi:EquipmentList |
Container for equipment nav items. |
EquipmentNavItem |
kvg:EquipmentNavItem sbsmi:EquipmentNavItem |
One equipment entry in the nav. |
FloorplanList |
kvg:FloorplanList sbsmi:FloorplanList |
Container for floorplan nav items. |
FloorplanNavItem |
kvg:FloorplanNavItem sbsmi:FloorplanNavItem |
One floorplan entry in the nav. |
CustomList |
kvg:CustomList sbsmi:CustomList |
Container for custom nav items. |
CustomNavItem |
kvg:CustomNavItem sbsmi:CustomNavItem |
One custom entry in the nav. |
AdminList |
kvg:AdminList sbsmi:AdminList |
Container for admin nav items. |
AdminNavItem |
kvg:AdminNavItem sbsmi:AdminNavItem |
One admin entry in the nav. |
ExternalList |
kvg:ExternalList sbsmi:ExternalList |
Container for external link items. |
ExternalLinkItem |
kvg:ExternalLinkItem sbsmi:ExternalLinkItem |
A link out to an external URL. |
SubSiteList |
kvg:SubSiteList sbsmi:SubSiteList |
Container for sub-site nav items. |
SubSiteNavItem |
kvg:SubSiteNavItem sbsmi:SubSiteNavItem |
One sub-site entry in the nav. |
Servlet |
kvg:Servlet sbsmi:Servlet |
Internal servlet. Not placed in the station tree by hand. |
Types in graphics and views
These live in .px files or are referenced as view ords, not in
the station database. Removing components from a bog does not touch them, and
they will still be broken afterwards. Fix them in Workbench.
| Type | Seen as | What it is |
|---|---|---|
Nhtml |
kvg:Nhtml sbsmi:Nhtml |
The view itself. Appears in nav files and px as an ord: view:nhtml:Nhtml. |
NhtmlRedirect |
kvg:NhtmlRedirect sbsmi:NhtmlRedirect |
Redirect view, referenced as view:nhtml:NhtmlRedirect. |
Common questions
What is the nhtml Niagara module?
Serves a responsive HTML5 navigation front end from a Niagara station. A single HTML5 service holds the nav structure and points at CSS/JS/nav files in the station file space.
Why does my station say the type kvg:HTML5 cannot be resolved?
That type belongs to the nhtml module. The station was built on a host with nhtml installed and is now running somewhere it is not. Either install the module, or remove the components that use it.
How do I remove nhtml from a station without Workbench?
Open the .bog with the tool on this site. It removes every nhtml component and any link left pointing at one, entirely in your browser, and gives you a report of what was taken out.
Your options
- Install the module. If you can get the jar and you are licensed to run it, this is the least disruptive path — nothing in the station changes.
- Remove the components. Use the tool on this site. The station loses that functionality but it will start and run.