Skip to Content
Browse documentation

Edit a Hosting Package in WAP

Update an existing Eenos package definition, preserve its identity and apply reviewed changes to intended accounts separately.

Open Hosting → Packages → All Packages, select Edit Package, confirm the selected name and enter the editor.

Identity and fields

Package Name cannot be renamed through this workflow. Editing requires an existing package definition. The editor uses the same resource, feature, sending-policy, CageFS, LVE, inode and Governor controls described in Add Package, initialized from the saved package.

Review every field, particularly default/custom resource modes and inheritance. A stored package from an older version may need newly available fields reviewed explicitly. Keep the prior definition if you may need to restore it.

Save Changes

  1. Confirm the package identity and intended changes.
  2. Review resource allocations, feature list, IP/shell choices and outgoing email ceilings.
  3. Review conditional CloudLinux settings and prerequisites.
  4. Select Save Changes.
  5. Confirm Save Package Changes, or cancel.
  6. Look for the package-saved success message and reload to verify.

The handler validates the complete form, updates the definition and records an audit event. Package ownership is retained rather than replacing it with the editing user's identity. Disabling LVE on a CloudLinux server saves LVE status Off while retaining the submitted/current CageFS preference.

Apply to existing accounts separately

No automatic account synchronization

The editor explicitly warns that existing accounts using the package are not updated by saving it. Use Upgrade or Downgrade for each intended account, selecting the reviewed plan, then verify account resource/feature values and actual enforcement.

Plan reassignment can replace custom account overrides. Its helper also excludes dedicated-IP and shell fields from the package-copy operation; a changed package IP/shell policy is not a promise that existing assignments change automatically.

Validation, errors and recovery

Package existence/name, required resources, numeric/unlimited values, sending ceilings and conditional CloudLinux checks apply as on creation. The current form rejects invalid or blank custom LVE limits and inconsistent numeric inode limits.

Missing package identity returns to the list. Demo sessions cannot apply edits. On unable-to-save or ownership/storage errors, inspect the actual saved definition before retrying; do not assume every step was rolled back.

Restore previous values through the editor if necessary. Accounts already reassigned need separate review; restoring the template alone does not revert them.

Do’s and don’ts

  • Do plan package and account synchronization as separate steps.
  • Do retain previous values and account-specific overrides.
  • Do verify every reassigned account afterwards.
  • Do not treat Save Changes as an automatic bulk account update.
  • Do not assume changing a package name field is a supported rename operation.

Return to Packages. Next sidebar group: Features.