WordPress management

The WordPress page combines common administrative actions with information gathered from the managed hosting node.

WP Admin one-click login

WP Admin creates a short-lived one-time sign-in token and posts it to WordPress. When Preview is enabled, the Panel prefers the Preview hostname so one-click login can work before production DNS and SSL have moved to Webcore.

If neither production HTTPS nor Preview is available, enable Preview first or use the site's normal WordPress login.

Plugins

The Panel inventories installed plugins and can perform supported plugin-management actions without exposing database credentials or shell access.

Uploaded plugins must be ZIP packages and are validated before installation. The current upload workflow limits plugin ZIP files to 50 MB. A failed upload/install leaves the existing site intact.

When changing a production plugin, use Staging first if the update could affect checkout, membership, booking or other important application behaviour.

Themes

The WordPress inventory also reports installed themes and the currently active theme. Theme state is useful when diagnosing a site that renders differently after an import, restore or deployment.

For source-controlled custom themes, prefer the managed Git deployment workflow rather than repeatedly copying theme files through the browser.

WordPress users

The Panel can manage WordPress users through the managed WordPress runtime. Passwords are handled as write-only values; the Panel does not retrieve existing WordPress passwords.

Treat administrator creation and password changes as privileged operations and remove temporary accounts when they are no longer needed.

Cache and debugging

WordPress controls expose supported cache and debugging state. When troubleshooting stale behaviour, identify the cache layer first: WordPress/plugin cache, Webcore Nginx Page Cache, Redis object cache or an external CDN can all produce different symptoms.

See Performance and caching for Webcore's server-side cache controls.

WP-Cron

Webcore distinguishes WordPress WP-Cron from managed Scheduled Tasks. Staging sites have WP-Cron disabled deliberately so a clone cannot execute production schedules unexpectedly.

See Scheduled Tasks for recurring server-side jobs managed by the platform.

Safe operating pattern

1. Use Preview when production DNS has not moved yet.
2. Use Staging for risky plugin, theme or configuration changes.
3. Keep a usable backup before destructive WordPress operations.
4. Clear only the cache layer relevant to the change being tested.
5. Validate WP Admin and important frontend application flows after changes.