With Portal Customization, the UniFi Controller software allows complete branding of a
portal implementation, allowing admins to white label the wireless Internet service as if
it were developed completely by the business. In order to provide the greatest degree of
flexibility in branding the company/individual, the UniFi Controller software provides total
access to the portal directory on the system in which it is installed. This open architecture
allows administrators to include unlimited content while keeping development simple
through the use of plain .html (hand code or use any text editor).
After enabling Portal Customization under the Guest Portal settings, the Controller creates
a file structure that can be easily accessed and navigated, found at /<unifi_base>/data/
sites/<site_name>/portal.
Among the files contained in the portal directory, the most important ones are outlined
below:
index.html – Main landing page that displays pricing, authentication information and
Terms of Use to the guest.
payment.html – Used to submit credit card information. It requires HTTPS and also
serves as an example of an additional .html page.
fail.html – Displayed when there is an error handling a guest login.
reset-min.css – Standardizes the rendering of HTML elements across browsers.
styles.css – Controls the style of HTML elements.
Located in the bundle folder are the following files:
bundle/messages.properties – This file defines package costs, duration of access,
package titles, and how the charge will appear on a customer’s credit card account.
Error messages are also defined by this file and can be edited in most text editors.
bundle/vouchers.css – Standardizes the rendering of HTML elements across browsers.
vouchers.html – The default appearance of vouchers belonging to a site.
Testing is simple and immediate; simply save code on the Controller PC, reload the guest
browser and see changes reflected on Guest Portal pages. All HTML pages are rendered
and can be the target of a form’s POST action. None of the supporting files are required
(e.g., styles, css), although using the files provided by Ubiquiti, network administrators
have complete control to customize the Guest Portal experience for the end-user.
Moreover, multiple hotspot packages can be configured for different payment types,
names, duration of use, bandwidth limits, etc.
ich habe den Fehler vermutlich gefunden. Es fehlte die Datei “terms.html”. Ein aptitude reinstall behob den Fehler. Allerdings konnte ich noch nicht vor Ort überprüfen obs jetzt funktioniert.
möglicheweise ist die Usache zu wenig Ram. In der Schule ist alles Xen virtualisiert. Es waren für den UNIFI-Controller 512 MB vogesehen. Bei der Suche nach dem Grund für das nicht funktionieren bin ich unter
/var/log/unifi
auf Fehlermeldungen gestoßen die nach dem Erhöhen des Speichers verschwunden sind.
Ob damit auch das eigentliche Problem behoben ist erfahre ich morgen.