All Features in WAP
List Eenos capability definitions and use edit/delete actions while reviewing dependent packages and hosting accounts.
Open Hosting → Features → All Features. The Available Features table has search, pagination and page-length controls.
Columns and controls
The columns are Feature Name, Owner, Addon Domains, Parked Domains, Subdomains, FTP, MySQL, DNS, Email, Backups and Action. Enabled/Disabled columns show only a subset of the complete list; inspect the editor for all 37 switches.
Create Feature opens Add Feature. The owner identifies the stored definition owner, not every package/account using it.
Edit
Select Edit Feature, review the named target and configuration notice, then confirm Edit Feature to enter the editor. That navigation step does not save values. Follow Edit Feature for the shared-policy implications.
Delete
Select Delete Feature, review the Feature name and Permanent Action notice, then confirm deletion or cancel. Demo sessions cannot delete. The default list is protected against deletion, including case-insensitive default handling in the delete view.
Deletion removes the definition file, not hosting accounts or their files. The current handler does not first enumerate or migrate every package/account reference to it. Review dependencies and choose replacement references through the appropriate configuration tools before removal.
No automatic reference repair or undo
Deleting a referenced list can affect users of that policy. Record the full switch set and affected references first. Recreating only the same name is not restoration of its original settings.
Errors and verification
The server checks that the selected list exists. Missing lists, protected-default errors, demo restrictions and unable-to-delete messages require reviewing actual definition state and logs before retrying. Package-feature collection can skip unreadable files; a missing row is not proof the definition or all references disappeared.
Actions record hosting-feature audit events. Verify intended definitions and affected user interfaces separately after a change.
Do’s and don’ts
- Do inspect the full editor rather than only the table's summary columns.
- Do review dependent packages/accounts before deletion.
- Do not confuse feature removal with customer termination.
- Do not assume deleting a file automatically repairs references.
Next: Add Feature.