--- title: "WP Toolkit and WP Blueprint — Documentation" url: "https://wordpane.cloud/en/documentacao/wordpress/" description: "Updates, plugins, themes, debug, cache, cron, security and installation patterns. See the steps and guidelines for using the WordPane Cloud panel." language: "en" generatedAt: "2026-10-30T19:14:01.421Z" contentType: "public-page" pricingSource: "https://app.wordpane.cloud/api/public/plan-catalog" --- [Documentation center](https://wordpane.cloud/en/documentacao/) Control panel # WP Toolkit and WP Blueprint 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. - Open the correct WordPress application and select WP Toolkit. - Check out WP Version and update indicators. - Review amounts of plugins, themes and users; to manage WordPress accounts, open the administration of the site itself. - For a planned maintenance, enable Maintenance Mode when you need to show a waiting page. - Do the procedure, test and disable the maintenance. Check out the public access later. - Use Manage Cron to open the schedule and View all themes to consult the themes. **Before continuing** The WordPress user summary is not the server Application Users list. WP Auto Login can open an administrative session: use only in the correct application and avoid sharing the session URL. ## 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. - Record the failure and time before changing debug. - Open Debug and check the status of the three controls. - For an investigation, enable collection and log as needed. - In production, keep Display Errors disabled to avoid exposure of paths and technical information. - Play the problem and see the corresponding record. - After diagnosing, review the need to maintain debug and monitor log growth. **Before continuing** Activating debug does not correct the error. Preserve useful messages and treat the cause in the plugin, theme or code. ## 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. - Make a recoverable copy of files and database and test important changes in staging. - Open Updates and check out the core and pending versions. - Apply the core update when appropriate and follow the result. - Review pending plugins and themes before updating in batch; consider dependencies and compatibility. - Check Database Update and the result of the necessary update routines. - Test pages, login, forms, purchases and integrations after operation. - If you used maintenance, deactivate upon completion and confirm public access. **Before continuing** Up to date indicates no update offered at that time, does not prove future compatibility. A copy of the files only does not recover a change made to the database scheme. ## 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. - Search the plugin or use the appropriate filter. - To add a component, click Install Plugin and use the displayed search/package options. - Check source, name and compatibility before installing. - Use Enable or Deactivate in the plugin line as desired operation. - Update when there is a version offered and test the function it controls. - For Uninstall, check if you no longer need the plugin and if your data/configurations need export before. **Before continuing** Disable and uninstall have different effects. Uninstallation can trigger data removal routines from the plugin itself. Premium plugins remain subject to license and supplier updates. ## 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. - Open Themes and get the theme. - Use Install Theme to add a theme to the options presented. - Check source, license and compatibility. - Before activating another theme, test in staging and check customizations and theme-child. - Activate only the desired theme and test pages, menus, forms and mobile version. - 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. - If the site shows old content, check first if the change is already published. - Use Flush Cache when you need to clear the WordPress cache. - Test the content in a new request and check separate proxy/CDN caches. - If permanent links return error after changes, check the URLs and use Flush Rewrite to regenerate the rules. - 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. - Test internal pages and administrative access. **Before continuing** Clear cache can temporarily increase server work while data is reconstructed. Flush Rewrite does not correct domain or DNS pointed to another server. ## 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. - Confirm Redis available and the valid license that will be used. - Open Object Cache Pro and check the state. - When enabling, fill in the settings and license key requested by the panel. - Save and test the operations of the site. - Check the status of the Redis component and consumption. If you change the Redis password from the server, update the corresponding consumers. **Before continuing** The form after the license was not changed in this review. Check the fields effectively displayed and the conditions of your license. ## 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. - Check out Current method. - Select WP Cron or Server Side Cron according to the project routine and click Save. - Confirm the saved method and test the execution of tasks. - With active WP Cron, use Run Now for events that have already arrived. - Keep Run all events unscheduled in normal routine. Mark all recorded events, even future ones; use only in a planned test or diagnosis. - Check out the results of the tasks within the app and its logs. **Before continuing** Cron can perform sending messages, processing and other actions with external effects. Do not force all events just to check if the button works. Avoid duplicate a routine already managed by Toolkit with another independent task without checking the behavior. ## 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. - Check which integrations depend on XML-RPC, such as WordPress applications and services. - Review the status and description of the XMLRPC Status control before changing; the section title and control status should be read together. - In PHP Execution Status, check the execution lock in the wp-content/uploads directory and plugin specific requirements. - Use Verify Checksums to compare core files with official checksums. - If there is a difference, check the reported files and investigate legitimate or unexpected changes; do not delete content automatically. - Test integrations, uploads and administration after changes in protections. **Before continuing** A core checksum does not check all plugin code, themes or uploads. Result without divergence does not replace complete security analysis. ## 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. - Back up the database and identify the exact source and destination text. - Fill in Search and Replacement. - Keep Dry run marked and click Preview. - Check the report and whether the replacement affects only the expected content. - Only after this conference, uncheck Dry run and review the application action presented before confirming. - Wait, test pages and links and see new errors. **Before continuing** Do not use broad or incomplete texts for a domain exchange. An incorrect replacement may change content that should remain. The simulation doesn't create a recovery copy. ## 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. - Check if it's a production site or a test environment. - Select appropriate language and time zone for the audience and site routines. - Review date/time formats, upload organization, and link structure. - Configure visibility/indexing according to the environment; test can stay out of indexing, production needs an intentional choice. - Save and check preferences on WordPress and public links. **Before continuing** Changing the link structure of an existing site requires checking old URLs and redirects. Deactivated indexing is not password access control. ## Create and apply a WP 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. - Open Create Blueprint and report Name. - In Themes and Plugins, use Add/Browse to select directory components or Custom for an authorized ZIP package itself. - Configure Site Language, Timezone, Date Format and Time Format. - Review Disable Search Engine Indexing and Organize Upload Folders. - Choose Permalink Structure; for a custom structure, check out the tags and preview. - In Cleanup, check out removal of Hello World, Sample Page, themes, plugins and unnecessary core files. - In Debug Settings, check out Debug Mode, Debug Log and Display Errors. Adjust for production or test use. - Click Create Blueprint and confirm the pattern in the list. - In creating a new WordPress application, select the default in Blueprint. - After installation, test components and check indexing, debug and applied preferences. **Before continuing** In the revised form, cleaning options, indexing deactivation and debug were initially marked. Review before creating a production pattern. Blueprint does not automatically include content, media, and database of an existing site; use backup or cloning for this. Plugin licenses and premium themes are independent of the saved default. Updated October 8, 2026. [Consult other guides](https://wordpane.cloud/en/documentacao/) --- Fonte oficial: https://wordpane.cloud/en/documentacao/wordpress/ Esta é uma representação da página pública. A data de geração não indica alteração editorial.