Install and update POM Theme

POM Theme is distributed as a private WordPress theme package named pom-latest.zip. The installed directory and canonical theme identity are both pom; do not rename the directory.

The current release metadata declares PHP 8.1 as the minimum. Check the WordPress compatibility and tested version shown with the release before installing it on production.

Before installation

Prepare:

• administrator access to WordPress;
• the current pom-latest.zip from My Account → Licenses & Downloads;
• a POM Theme license key for the site or network;
• a current database-and-files backup;
• a staging site when the project includes custom code, dynamic templates, forms, or business-critical WooCommerce flows.

If another theme is active, record its widgets, menu assignments, templates, and theme-specific content before switching. WordPress preserves content records, but another theme's presentation and settings do not become POM Theme configuration automatically.

Install on a single site

1. Open Appearance → Themes.
2. Select Add New Theme.
3. Select Upload Theme.
4. Choose pom-latest.zip, then install it.
5. Activate POM.
6. Keep the Compile assets tab open after POM redirects there. Activation creates any missing Theme Option files from their defaults and immediately starts the first complete CSS and JavaScript compilation.
7. Wait for the progress bar to reach 100% and confirm that the success message appears.
8. Open Settings → POM Theme → License.
9. Save and validate the POM Theme license key.
10. Visit the frontend and confirm that WordPress can load the theme without a fatal error or missing-asset response.

The package contains one top-level pom directory. A ZIP with another root name or without the production dependencies is not the official installable artifact.

Install on multisite

1. Open Network Admin → Themes.
2. Select Add New and upload pom-latest.zip.
3. Make POM available to the intended sites.
4. Activate POM on the network main site when the local theme updater must participate in network update checks.
5. Open the main site's Settings → POM Theme → License as a network administrator.
6. Save and validate the network license.
7. Activate POM on each subsite that will use it.
8. On each subsite, wait for the automatic Compile assets run to finish before reviewing its frontend.

Network-enabling a theme makes it selectable on subsites; it does not execute that theme on the main site. POM Theme reads one network-scoped license for multisite updates.

Activation never replaces existing POM settings. If a configured site switches away from POM and later reactivates it, only missing settings files are restored from current defaults before the complete build starts.

Verify a new installation

• Appearance → Themes shows POM as active on the intended site.
• The activation compilation finishes successfully under Settings → POM Theme → Tools → Compile assets.
• The frontend, login, and WordPress administration load normally.
• Settings → POM Theme opens for the intended role.
• The License section shows a valid connection.
• Dashboard → Updates can complete a theme update check.
• Existing menus are assigned to the POM locations required by the selected header.
• Existing widgets are reviewed under Appearance → Widgets.

Continue with Configure and review your first POM site. Do not enable every optional POM system merely because it is available.

Apply an automatic update

With a valid license, POM Theme uses the standard WordPress theme-update interface.

1. Read the release notes.
2. Back up the database and files.
3. Verify the update on staging when the site has custom code or critical workflows.
4. Open Dashboard → Updates or Appearance → Themes.
5. Run the POM Theme update.
6. Confirm the installed version.
7. Review the frontend, editor, generated styles, templates, forms, and WooCommerce journeys affected by the release.
8. Refresh the relevant origin and edge caches only after the updated source behavior is correct.

The licensed updater verifies the downloaded package before WordPress installs it.

On multisite, run theme updates from Network Admin → Dashboard → Updates and verify representative subsites after the files change.

Replace the package manually

Use a manual replacement when the current package is available from the account but WordPress does not offer the automatic update:

1. Create a current backup.
2. Download the new pom-latest.zip.
3. Open Appearance → Themes → Add New Theme → Upload Theme.
4. Upload the ZIP.
5. Choose WordPress's option to replace the installed theme with the uploaded version.
6. Confirm the POM version and repeat the relevant functional checks.

Do not delete the active theme first on a production site. Replacing the package changes theme code while preserving WordPress content and the site's POM settings.

If no update appears

Check in this order:

1. Settings → POM Theme → License reports a valid connection.
2. The subscription is active and the current domain is authorized.
3. WordPress can make outbound HTTPS requests to the POM account service.
4. WordPress update checks are not being held by a stale transient or deployment cache.
5. On multisite, the network license is configured on the main site and the update is being checked from Network Admin.
6. When relying on the theme's local updater, POM is active on the main site.

The site continues to render if the account service is temporarily unreachable, but validation, update discovery, and downloads can be delayed.