WordPane
Documentation center
Control panel

WordPress Toolkit and Blueprints

Updates, plugins, themes, debug, cache, cron, security and installation patterns.

Control Panel Guide

The procedures below take place inside the server. The English labels help locate the controls on the screen. Account, balance and hiring belong to the client area.

Read the overview and use maintenance

Where to find: WordPress Application → WP Toolkit → Overview

Overview features kernel version, active/inactive plugins, themes, users, active theme and cron events. WP Auto Login is an access to site administration.

  1. Open the correct WordPress application and select WP Toolkit.
  2. Check out WP Version and update indicators.
  3. Review amounts of plugins, themes and users; to manage WordPress accounts, open the administration of the site itself.
  4. For a planned maintenance, enable Maintenance Mode when you need to show a waiting page.
  5. Do the procedure, test and disable the maintenance. Check out the public access later.
  6. Use Manage Cron to open the schedule and View all themes to consult the themes.

Diagnose errors without exposing them to visitors

Where to find: WP Toolkit → Debug

Debug Mode collects warnings and errors; Debug Log saves messages; Display Errors shows errors on the page. These are three different options.

  1. Record the failure and time before changing debug.
  2. Open Debug and check the status of the three controls.
  3. For an investigation, enable collection and log as needed.
  4. In production, keep Display Errors disabled to avoid exposure of paths and technical information.
  5. Play the problem and see the corresponding record.
  6. After diagnosing, review the need to maintain debug and monitor log growth.

Update core, plugins, themes and database

Where to find: WP Toolkit → Updates

The WordPress Core, Plugin Updates, Theme Updates and Database Update sections allow you to track components. An update may require database changes.

  1. Make a recoverable copy of files and database and test important changes in staging.
  2. Open Updates and check out the core and pending versions.
  3. Apply the core update when appropriate and follow the result.
  4. Review pending plugins and themes before updating in batch; consider dependencies and compatibility.
  5. Check Database Update and the result of the necessary update routines.
  6. Test pages, login, forms, purchases and integrations after operation.
  7. If you used maintenance, deactivate upon completion and confirm public access.

Install and manage plugins

Where to find: WP Toolkit → Plugins

The table presents name, status, version and update. There are All, Active, Inactive and Updates Available filters and search by name.

  1. Search the plugin or use the appropriate filter.
  2. To add a component, click Install Plugin and use the displayed search/package options.
  3. Check source, name and compatibility before installing.
  4. Use Enable or Deactivate in the plugin line as desired operation.
  5. Update when there is a version offered and test the function it controls.
  6. For Uninstall, check if you no longer need the plugin and if your data/configurations need export before.

Install and manage themes

Where to find: WP Toolkit → Themes

Use the active theme as a reference before changing the look. An installed theme is not necessarily the theme in use.

  1. Open Themes and get the theme.
  2. Use Install Theme to add a theme to the options presented.
  3. Check source, license and compatibility.
  4. Before activating another theme, test in staging and check customizations and theme-child.
  5. Activate only the desired theme and test pages, menus, forms and mobile version.
  6. Remove unused themes only after conferring dependencies and maintaining a recovery.

Wipe cache and regenerate link rules

Where to find: WP Toolkit → Performance

Flush Cache removes cache data; Flush Rewrite regenerates permanent link rules. Operations deal with different problems.

  1. If the site shows old content, check first if the change is already published.
  2. Use Flush Cache when you need to clear the WordPress cache.
  3. Test the content in a new request and check separate proxy/CDN caches.
  4. If permanent links return error after changes, check the URLs and use Flush Rewrite to regenerate the rules.
  5. The observed screen informs Soft Flush, which updates rules in the database. If there is hard flush option, check out the effect also on .htaccess before using.
  6. Test internal pages and administrative access.

Configure Object Cache Pro when needed

Where to find: WP Toolkit → Object Cache Pro

Object Cache Pro uses Redis to cache objects and requests a license. Redis installed does not mean that this component is configured.

  1. Confirm Redis available and the valid license that will be used.
  2. Open Object Cache Pro and check the state.
  3. When enabling, fill in the settings and license key requested by the panel.
  4. Save and test the operations of the site.
  5. Check the status of the Redis component and consumption. If you change the Redis password from the server, update the corresponding consumers.

Choose WP Cron or Server Side Cron

Where to find: WP Toolkit → Cron

WP Cron performs tasks when the site receives visitors. Server Side Cron uses a server task to reduce visitor dependency.

  1. Check out Current method.
  2. Select WP Cron or Server Side Cron according to the project routine and click Save.
  3. Confirm the saved method and test the execution of tasks.
  4. With active WP Cron, use Run Now for events that have already arrived.
  5. Keep Run all events unscheduled in normal routine. Mark all recorded events, even future ones; use only in a planned test or diagnosis.
  6. Check out the results of the tasks within the app and its logs.

Review core protections and integrity

Where to find: WP Toolkit → Security

The page brings together XML-RPC, PHP execution in uploads and Verify Checksums. Checking integrity and blocking requests are different actions.

  1. Check which integrations depend on XML-RPC, such as WordPress applications and services.
  2. Review the status and description of the XMLRPC Status control before changing; the section title and control status should be read together.
  3. In PHP Execution Status, check the execution lock in the wp-content/uploads directory and plugin specific requirements.
  4. Use Verify Checksums to compare core files with official checksums.
  5. If there is a difference, check the reported files and investigate legitimate or unexpected changes; do not delete content automatically.
  6. Test integrations, uploads and administration after changes in protections.

Simulate and apply a replacement to the seat

Where to find: WP Toolkit → Search & Replacement

The tool searches and replaces text in the WordPress tables. Dry run allows you to check matches without saving changes.

  1. Back up the database and identify the exact source and destination text.
  2. Fill in Search and Replacement.
  3. Keep Dry run marked and click Preview.
  4. Check the report and whether the replacement affects only the expected content.
  5. Only after this conference, uncheck Dry run and review the application action presented before confirming.
  6. Wait, test pages and links and see new errors.

Configure language, formats and indexing

Where to find: WP Toolkit → Settings

The page brings together website language, time zone, formats, permanent links and visibility for searchers.

  1. Check if it's a production site or a test environment.
  2. Select appropriate language and time zone for the audience and site routines.
  3. Review date/time formats, upload organization, and link structure.
  4. Configure visibility/indexing according to the environment; test can stay out of indexing, production needs an intentional choice.
  5. Save and check preferences on WordPress and public links.

Create and apply a WordPress Blueprint

Where to find: Server → WP Blueprint → Create Blueprint

Blueprint is a standard for new installations: themes, plugins, preferences, cleaning and debug. Review all options, not just the name.

  1. Open Create Blueprint and report Name.
  2. In Themes and Plugins, use Add/Browse to select directory components or Custom for an authorized ZIP package itself.
  3. Configure Site Language, Timezone, Date Format and Time Format.
  4. Review Disable Search Engine Indexing and Organize Upload Folders.
  5. Choose Permalink Structure; for a custom structure, check out the tags and preview.
  6. In Cleanup, check out removal of Hello World, Sample Page, themes, plugins and unnecessary core files.
  7. In Debug Settings, check out Debug Mode, Debug Log and Display Errors. Adjust for production or test use.
  8. Click Create Blueprint and confirm the pattern in the list.
  9. In creating a new WordPress application, select the default in Blueprint.
  10. After installation, test components and check indexing, debug and applied preferences.

Updated October 8, 2026.

Consult other guides