Install cPAddons Site Software — Simple & Complete Guide

Install cPAddons Site Software — Simple & Complete Guide

This interface lets you add and manage cPAddons and their vendors. cPAddons are ready-made applications your users can install for their sites (for example blogs, forums, or online stores).

Important:
  • This interface is deprecated in versions starting at 104 and may be removed in future releases.
  • This interface does not appear on servers running Ubuntu.

Package-Manager Install (WordPress)

WordPress installs through a package manager. The installer package is the unmodified release from wordpress.org. When installed this way, you can update WordPress from its own admin panel.

Behind the scenes, the interface discovers, installs, and removes packages via the system package manager (for example yum).

Note:
  • Older “WordPress (legacy)” was deprecated in v64 and disabled in v70.
  • To migrate legacy installs to the modern package-manager WordPress cPAddon, run:
/scripts/migrate_legacy_wordpress_to_modern_wordpress

Security Notes

Some cPAddons include files that store credentials. On shared servers that do not use one of the following, you must harden file permissions to avoid cross-user exposure:

  • mpm-itk
  • mod_ruid2
  • mod_suphp

Some cPAddons may show lower security ratings due to inherent risks in certain PHP patterns. Review your PHP hardening policy before enabling widely.

Install a cPAddon

  1. Select the Installed checkbox next to the cPAddon you want.
  2. (Optional) Select Force Refresh of All cPAddon Sources if you suspect corruption and want to refresh source files.
  3. Click Update cPAddon Config. Wait for completion, then click Back.

Newly enabled cPAddons are available in feature lists by default (Feature Manager).

Add New Vendors

You can extend the catalog by adding vendor information URLs:

  1. Paste the vendor’s URL into Vendor’s Information URL.
  2. To add more vendors at once, choose how many extra URL fields you want, click Add additional URL fields, and fill them in.
  3. Click Update Vendors. When it finishes, click Back.

This supports third-party developers who publish their own cPAddons.

Delete a Vendor

  1. In Add or Remove Vendors, tick the vendor under the Remove column.
  2. Click Update Vendors and confirm. Then click Back.

Note: You cannot remove individual cPAddons from the list—removal is at the vendor level.

What Happens to Data When a Vendor Is Removed?

  • If the cPAddon originally created the database and nothing else uses it, the database is dropped (including user-created tables within it).
  • If the cPAddon didn’t create the database or another cPAddon still uses it, only the tables for the removed cPAddon are dropped. This may leave an empty database behind.
  • Best practice: remove any other cPAddons that share a database before deleting the one that created it. Otherwise, you’ll need to manually remove the leftover empty database.

You can manually delete empty databases in the user’s database management interface.


Quick Reference

  • Enable/Disable for users: via Feature Manager.
  • Refresh sources when needed: use Force Refresh of All cPAddon Sources.
  • Modern WordPress installs: managed via package manager; update from WordPress admin.
  • Legacy WordPress migration:
/scripts/migrate_legacy_wordpress_to_modern_wordpress
case studies

See More Case Studies