Your workspace, explained.

Free

Start here

Corevum is a workspace for managing a WordPress website. It brings content, media, forms, plugins and site tools together while keeping WordPress as the underlying system. It does not migrate your content into a separate service. Your pages, products, users and media remain in your WordPress installation.

This guide covers Corevum Free and Pro 1.1.0. Some screens depend on your role, enabled modules and other installed plugins. Corevum Free is the base plugin. Corevum Pro is a separate add-on and must be installed alongside Free. WooCommerce and Gravity Forms are separate products; their integrations require those plugins.

Start with the Free workspace on a staging copy of your website. Confirm that your existing editor, forms, shop and plugin settings behave as expected before changing the live site's workflow. Corevum does not guarantee compatibility with every theme, plugin or hosting configuration.

Free + Pro

Install and update the plugins

Corevum requires WordPress 6.2 or later and PHP 8.1 or later. Corevum Pro 1.1.0 requires Corevum Free 1.1.0 or later. Update Free first, then Pro. Use a current supported WordPress and PHP release where your hosting and other plugins permit it. Keep a backup of the database and uploaded files, and make sure you can access your hosting file manager if you need to recover an interrupted update.

Download Free from the Corevum product page. Download Pro from the Dawsony account used for the purchase. Do not upload the source repository, brand pack or a ZIP containing both plugins as one plugin. Install each release ZIP separately. Free does not require a Dawsony account or licence activation.

Network activation and multisite workflows are not covered by a confirmed support guarantee for this release. Test on an individual staging installation and contact support before planning a network rollout.

1. In WordPress, open Plugins > Add New > Upload Plugin and choose the Corevum Free release ZIP.
2. Install and activate Corevum, then open Corevum from the administration menu.
3. If you purchased Pro, install its separate ZIP and activate it while Free remains active.
4. Open Plans & licence to activate Pro, then review Modules and enable the tools you need.

Free

Find your way around

The overview is the starting point for content and site activity. The sidebar groups your working areas and management tools. Open Content for pages, posts and registered content types; use Media library for attachments and folders. The available menu changes with capabilities and installed integrations.

Press Cmd+K on macOS or Ctrl+K on Windows to open the command palette. Search for a destination or content item instead of hunting through menus. The palette remembers recent destinations in your browser, which can include content titles and admin URLs. On a shared computer, use a separate browser profile and sign out when you finish.

Classic WordPress opens the native administration experience. Use it whenever a third-party workflow needs its original screen. Returning to classic does not uninstall Corevum or move your content. Corevum also wraps many native screens, so a native editor inside the Corevum shell is expected behaviour.

Free

Theme, sidebar and personal preferences

Choose light or dark mode using the workspace theme control. Your theme preference is saved to your WordPress user, so another administrator can choose a different appearance. The system preference is used until you choose. Some embedded WordPress or third-party editor panels retain their own light appearance to keep their controls readable.

The sidebar can collapse to give more room to your work. On narrow screens, open navigation when you need it and close it before editing. Tables and specialised native plugin screens may need horizontal scrolling on a phone. Use a tablet or desktop for complex variations, bulk edits and theme editing.

Corevum stores workspace preferences in WordPress user metadata. Media view choices and command-palette history also use browser local storage. These are functional preferences, not an analytics service.

Free + Pro

Choose modules without losing data

Open Modules to see the available features and their dependencies. Most everyday Free modules are enabled initially. Performance starts disabled. The Pro Header & footer code module also starts disabled. Pro modules need an available Pro entitlement; commerce also needs WooCommerce and the Gravity Forms entry view needs Gravity Forms.

Switching off a module stops its hooks, screens and related behaviour. It does not delete its saved configuration or content. Re-enabling it restores access to that data. This distinction matters for public features: a disabled Forms module stops rendering its forms, and disabling a custom post type definition can make its public URLs unavailable even though its posts still exist.

If you already use ACF, Gravity Forms or another content-model or form plugin, keep the existing tool for that job unless you deliberately migrate it. Corevum's conflict hints identify overlapping tools; they do not automatically convert their data. Avoid registering the same post-type or taxonomy slug in two plugins.

1. Review each module and the plugin dependency shown beside it.
2. Switch off features you do not need, one at a time.
3. Check the public website after changing forms, content types, redirects or performance settings.
4. Re-enable the module if a required screen or public feature disappears.

Free

Pages, posts and content editing

Content lists posts, pages and supported custom post types. Use the search and available status filters to find an item. Editing opens the appropriate WordPress editor so Gutenberg blocks, editor settings and compatible plugin panels remain available. Corevum is not a replacement block format.

Duplication creates a draft copy with terms and custom fields. Review the copied title, slug, SEO metadata, images and any plugin-specific identifiers before publishing. Bulk status changes affect every selected item; check the selection before moving content into draft or trash.

From version 1.0.1, choose Trash in the status filter to restore deleted pages, posts and supported custom content. Restore from a row or select several and choose Restore selected. WordPress restores content as a draft by default; review it before publishing. WordPress controls Trash retention, and site-specific restoration hooks are respected. Changing the status filter clears selections; failed bulk actions stay selected for retry.

If a field panel is missing, confirm that the providing plugin is active, the field group applies to that post type, and the panel is enabled in the editor's preferences. ACF fields are managed by ACF; Corevum's own field groups do not import them. Use Classic WordPress to distinguish an editor/plugin issue from a Corevum presentation issue.

Free

Categories, tags and custom taxonomies

Categories and tags organise content independently of the content itself. Select the relevant taxonomy, create a term and assign it when editing content. Hierarchical taxonomies support parent-child organisation; drag-and-drop nesting changes the term hierarchy rather than moving the posts into another post type.

Use the Taxonomies module when you need a new grouping such as Project type or Team department. Choose a stable slug, decide whether it is hierarchical, and attach it to the appropriate content types. Slugs become part of integrations and sometimes URLs, so avoid renaming them casually after content has been published.

After a structural change, check the public archive and individual content URLs. Corevum schedules rewrite-rule refreshes for definition changes. If URLs still return 404, confirm that the module is enabled and the content is published, then use WordPress Permalinks to refresh the site's rewrite rules.

Free

Media library, folders and bulk work

The media library works with WordPress attachments. Folders are organisational labels; moving an attachment into a folder does not move the physical file or change its URL. Nested folders also appear in the WordPress media picker when the Media folders module is enabled.

Use selection controls for supported bulk operations such as downloads, metadata changes and deletion. ZIP downloads depend on your server's archive support and available resources. For a large library, work in smaller batches and confirm the downloaded archive opens before relying on it as an export.

Titles, alternative text, captions and descriptions have different purposes. Write alternative text to convey an image's purpose in context; a filename repeated as alt text rarely helps. A caption is visible accompanying text when the theme or block displays it. Updating these values does not automatically rename every physical upload or change every existing block's markup.

Deleting an attachment can remove the underlying file and break existing pages that use it. Downloading selected files is not a full website backup because it does not include all attachment metadata, database records or page content.

Free + Pro

Edit images and replace files

With Image editor enabled, open an image to crop, rotate, flip or resize it. Review the preview and the resulting dimensions before saving. The editor keeps an original for its restore workflow, but that is not a substitute for a backup of your uploads directory.

Pro adds bulk featured-image tools and file replacement. Featured images belong to content items and are separate from images inserted into page content. Choose the supported content type, inspect the selected posts and confirm the replacement image before applying a bulk change.

File replacement is useful when a document or image must keep its existing address. Check file type and size restrictions in the interface. After replacing a file, clear relevant website/CDN caches and check pages that reference it. A browser can continue showing an older cached copy even when the replacement succeeded.

Free

Build and publish a form

Forms can start from a template or your own fields. Available field types include text, email, phone, paragraph, number, URL, date, dropdown, radio buttons, checkboxes, consent and headings. Use clear labels, explain required information and collect only what you need. A consent checkbox is a field, not a complete legal consent-management system.

The form's settings control the submit button, confirmation message or redirect, entry storage and email notification. Entry storage and notifications are enabled by default. You can disable either independently. If both are off, submitted information will not be retained by those two Corevum mechanisms.

Add the Corevum Form block in Gutenberg and choose the form, or use the shortcode below with your actual form ID. The form uses your theme's fonts and colours. It supports ordinary submissions without JavaScript and submits in place when JavaScript is available.

1. Create the form, add and label its fields, and mark only necessary fields as required.
2. Set the confirmation behaviour, storage choice and notification recipients.
3. Save the form and place it on a draft page using the Form block or shortcode.
4. Test as a signed-out visitor, including required-field errors, email delivery and the confirmation.
5. Publish the page and include the form in your privacy and retention process.

[corevum_form id="123"]

Free

Email delivery and spam protection

Notifications use WordPress wp_mail() and therefore your site's existing mail configuration, SMTP plugin or mail provider. Corevum does not provide a separate delivery service. A successful form submission does not prove that an email reached the inbox. Keep entry storage enabled if you need a second place to check enquiries.

Notification placeholders include {form_title}, {site_name}, {admin_email} and submitted field names in braces. Recipients can be comma-separated email addresses. Reply-to can use the submitted email field; test the result with a real address and verify your sender domain's mail setup.

Spam protection uses a hidden honeypot, a signed time check and a rate limit. The default permits up to ten submissions per visitor window. The visitor key is a salted HMAC derived from the request IP address and kept in an expiring transient for ten minutes after the latest attempt. Raw IP addresses are not stored in Corevum form entries. Your hosting or mail provider may keep its own logs.

If legitimate submissions fail, check page-cache behaviour and repeat from a signed-out browser. Repeated tests may trigger the limit. Do not disable site security or expose private entries just to diagnose mail delivery.

Free

Manage entries and privacy requests

Entries store field values, a form identifier, time, status, submitted email address where available, source URL and the logged-in user ID where applicable. Authorised users can read entries, change their status and export CSV. CSV exports and email copies contain personal data and need appropriate access controls outside WordPress too.

Automatic form entry cleanup is disabled by default. Administrators can enable a per-form age limit of 30, 90, 180 or 365 days; daily WordPress cron removes older entries in bounded batches while Forms is enabled. Decide how long enquiries are needed, review old entries and permanently delete those you no longer need. Moving an entry to spam or trash should not be treated as erasing all copies. A database backup, exported CSV or recipient mailbox can still contain the submission.

Corevum registers form-entry exporters and erasers with WordPress personal-data tools. Requests are matched by the stored email address. Keep the Forms module enabled while processing those requests. Entries without a matching email address, third-party form data, email copies and backups require separate review.

1. Open the form Entries view and use search/status filters to find the submission.
2. For a formal privacy request, use WordPress Tools > Export Personal Data or Erase Personal Data and its verification workflow.
3. Review any remaining exports, mailboxes and backups under your own retention process.
4. Document your retention period and contact route in the website privacy policy.

Free

Create a custom post type

A custom post type is useful for structured content such as Projects, Team members or Testimonials. Give it a stable machine slug and clear singular/plural labels. Choose whether it needs an archive and which editor features it supports. Corevum registers the definition; your theme determines how published content and archives look.

Do not reuse WordPress-reserved slugs or a slug already provided by WooCommerce, ACF, another plugin or your theme. If another system already owns the type, keep that system enabled and manage its content through the workspace instead of defining it again.

Changing a slug is not a content migration. Disabling or removing a definition leaves the underlying posts in the database but can hide their editor screens and public routes. Plan an equivalent registration or an explicit migration before retiring a content type. Test archive links, single-item pages, search and permissions after setup.

Free

Custom fields and template output

Create a field group, choose the content types it applies to and add named fields. Supported choices include text, paragraph, number, email, URL, date, selection controls, yes/no, image and colour. Keep machine names stable once content or templates refer to them. Corevum field groups and ACF field groups are separate systems.

Field values are ordinary post metadata. Registered fields are exposed through the WordPress REST API subject to the content and API permissions. Do not use them for passwords, API credentials or other secrets. Decide deliberately which values belong on public content.

Use the shortcode below for a value in content, or the PHP helpers in a theme template. The rendering helper produces escaped output for supported field types. When using raw values from corevum_get_field() or get_post_meta(), validate the expected type and escape for the destination context. Guard helper calls if the field module may be disabled.

1. Create the field group and attach it to the intended content type.
2. Edit a content item and save a test value in the field panel.
3. Add the output to your template or content and view it as a signed-out visitor.
4. Check draft/private content and role permissions before relying on fields for restricted information.

[corevum_field name="project_client"]

<?php
if (function_exists('corevum_the_field')) {
    corevum_the_field('project_client');
}
?>

Free

Comments and notifications

Use Comments to approve, reply, mark spam or move comments to trash, individually or through the available bulk controls. WordPress moderation settings and capabilities still apply. Corevum does not replace the site's comment form or anti-spam provider.

The notification bell opens workspace notifications; Inbox provides a fuller view of items needing attention. Dismissing a notice is not the same as resolving its underlying update, moderation or site-health issue. Open the relevant screen and verify the issue there.

Comment avatars can use WordPress's Gravatar configuration. If your privacy requirements prohibit external avatar requests, review Discussion settings and your existing avatar plugins. Corevum does not provide a separate anonymisation service for comments.

Free

Plugins, themes, updates and Site Health

Plugins shows installed extensions and available management actions. Active/inactive status and updates depend on WordPress's own plugin state. Your account needs the corresponding capabilities to activate, delete or update plugins. Corevum does not bypass host restrictions or filesystem permissions.

Themes and Updates bring WordPress management into the workspace. Some actions run through native WordPress screens so confirmation, upgrade progress and third-party hooks keep working. Use Classic WordPress if an extension needs its original screen. Themes still control the public website; changing a theme can change layouts and available editor features.

Use Site Health for WordPress's diagnostics. A good status is not a security audit or a guarantee of plugin compatibility. Back up before bulk updates, update on staging first where possible, and check the public website after completion. Update Free before Pro when Pro requires a newer base version.

If an update stalls, inspect the displayed error and hosting logs. Do not repeatedly retry while another updater is running. For an interrupted maintenance state or inaccessible dashboard, use your host's recovery tools and restore a known-good backup if needed.

Corevum 1.0.1 adds content Trash restoration and safer bulk selections. Corevum Pro 1.0.1 adds native View details information and includes minimum WordPress requirements in update metadata. Update both plugins to get these improvements.

Free + Pro

Native screens, ACF and WooCommerce

Corevum brings compatible native plugin screens into its shell and provides an Integrations area for third-party menus. WordPress Tools and Settings have dedicated workspace destinations. Some full-screen builders retain their original interface. Their own plugin permissions, notices and settings remain authoritative.

For products and orders, native WooCommerce editors preserve advanced options such as variations and extension-provided wholesale pricing fields. The enhanced Pro commerce views require WooCommerce to be active, the Store workspace module enabled and an account with the appropriate WooCommerce capabilities. Corevum does not include WooCommerce or grant access to orders to unauthorised roles.

If Commerce is missing, check those dependencies and sign in with an appropriate store-management account. If an ACF panel is missing, check its field-group location rules and Gutenberg panel preferences before changing Corevum settings. Test save/reload behaviour for any plugin-specific fields you depend on.

Gravity Forms entry browsing in Pro requires Gravity Forms and does not replace that plugin's form builder, licence or data policies. Disabling Corevum's own Forms module does not delete Gravity Forms forms.

Free + Pro

Header code and performance controls

From version 0.7.1, Header & footer code is available only in the separately installed Pro add-on. Existing snippet settings from Free 0.7.0 are preserved, but Free 0.7.1 does not execute them. Before upgrading, arrange a replacement or install the updated Pro add-on if you need those snippets to continue running. Header & footer code lets authorised administrators add website snippets without editing the theme. It is disabled by default and requires permission to use unfiltered HTML. Scripts you add can send visitor data to external analytics or advertising services, and can affect page security and performance. Corevum does not automatically obtain visitor consent for those scripts.

Performance controls are also disabled by default. They can remove features such as emoji scripts, embeds, XML-RPC or jQuery Migrate. Change one setting at a time and test the website, contact forms, checkout and any mobile or remote publishing integrations. A feature that looks unused may be required by another plugin.

If a change breaks a workflow, reverse the relevant switch and clear caches. These controls are not a substitute for measuring hosting performance, optimising images or reviewing expensive plugins. Keep a record of changes so the next administrator knows what was disabled and why.

Pro

Activate Pro and move a licence

After purchase, sign in to the Dawsony account used at checkout to obtain the Pro ZIP and licence key. Install Pro alongside Free, then open Plans & licence and activate the key for this website. Keep the key private: it authorises paid services and must not appear in screenshots or public support posts.

Activation sends the licence key, website hostname and Corevum product identifier to Dawsony over HTTPS. A scheduled daily check revalidates saved licences when WordPress cron runs. Authorised update checks also send the installed Pro version. These requests do not include your form submissions, posts or customer orders.

Plans cover 1, 5 or unlimited activated hostnames. A separate staging hostname counts as another site; this release does not automatically exempt staging. Installations under different paths on the same hostname are not represented as independent hosts by the plugin's activation request.

Before moving to a new hostname, deactivate the licence on the old installation while it can reach Dawsony. Then activate it on the destination. If the old site is unavailable or your activation limit is reached, contact support with the account email and relevant domain names. Do not post the key publicly.

Pro

Subscriptions, renewals and cancellation

Freelance covers 1 website at £9 monthly or £90 yearly. Pro covers 5 websites at £19 monthly or £190 yearly. Agency covers unlimited websites at £39 monthly or £390 yearly. Every plan includes the same Pro features, including white-label branding. Annual billing saves two monthly payments and is charged in full at the start of each year.

Subscriptions renew automatically until cancelled. Use Manage Billing in your Dawsony account to manage payment details and cancel future renewals. Cancellation normally keeps paid updates, downloads and support available until the end of the period already paid for. Cancelling renewal is not itself a refund request.

The purchase terms shown at checkout and emailed with the licence apply to your order. The initial purchase has a 14-day refund window; request it through info@dawsony.com with your account email or payment reference. A refund ends the associated paid entitlement. Read the linked refund policy and terms for the full conditions and statutory rights.

A normal expiry preserves previously activated Pro functionality on that installation, while paid downloads, updates and support end. Explicit revocation or deactivating the licence can disable Pro access. A temporary licence-service outage preserves the last valid local state. Keep a current subscription for ongoing updates and support; do not rely on an expired licence for a new activation.

Pro

White-label branding and client views

White-label controls let you apply your logo, workspace colours, favicon and footer, and customise the login presentation. Start with a transparent logo that remains legible at the actual displayed size. Check both workspace themes and the signed-out login page, not just a large source image.

Client view simplifies presentation for the people maintaining a site. Presets help repeat a workspace setup across sites. Inspect an exported preset before sharing it, and test the imported result on staging before using it for a client handover. A presentation profile is not a security boundary.

Menu editor lets you rename, reorder and hide menu destinations for roles. Hiding a menu does not remove the underlying WordPress capability or block a direct URL. Use Roles & capabilities when access itself must change, and verify the result with a separate test user.

Login destinations can send roles to the workspace, classic dashboard, their profile or the public site. Keep one known working administrator account while changing role menus and login destinations, so you have a recovery route if a configuration is too restrictive.

Pro

Roles, capabilities and safe handovers

WordPress capabilities determine who may publish, manage users, install plugins or change site settings. Corevum's role editor provides a friendlier way to adjust them, but the consequences are the same as changing WordPress permissions directly.

Create or copy a role for a client rather than experimenting on the only administrator role. Assign only the capabilities needed for the person's work. Do not grant unfiltered HTML, plugin installation or user-management powers merely to make a missing menu appear. Third-party plugins may define additional capabilities that need their own documentation.

The role tool includes restore support for its original role snapshot. Restoring a snapshot can overwrite subsequent role changes, so review the current configuration first. Always test access using the actual client's role and check direct links as well as the sidebar.

1. Keep a separate administrator account with a verified login.
2. Create or copy the intended client role and assign the smallest useful set of capabilities.
3. Apply menu and client-view preferences separately from access controls.
4. Sign in as a test user of that role and verify allowed actions and denied actions.
5. Record the final role, enabled modules and recovery contact in the handover.

Pro

Redirects and missing-page logs

Redirects map old paths to new destinations. Use 301 for a permanent move, 302 or 307 for a temporary route where appropriate, and 410 when a resource is intentionally gone and has no replacement. Test with a private browser or an HTTP client because browsers can cache permanent redirects.

Path matching normalises case and trailing slashes. Query parameters are carried to a destination that does not define its own query string. Check this behaviour for campaign links, searches and URLs containing private information before creating an external redirect. Avoid redirect loops and chains.

The missing-page log records normalised paths, hit counts and last-seen times. It does not record visitor IP addresses or user agents in that table, but the path itself can contain identifying information. The log is bounded by periodic trimming around 500 recent paths rather than an exact time-based retention promise. Review and clear it when needed.

If another redirect plugin owns the site's routing, leave that tool in control or plan a deliberate migration. Do not create competing rules in several plugins and assume their execution order will remain the same.

Pro

Activity history and maintenance mode

Activity history records selected sign-in, content, media, plugin, theme, user and settings events. Records can include user IDs, display names, login names, object identifiers, titles and event summaries. Failed sign-in events can include the submitted username. This is an operational log, not a complete forensic record of every action.

The default cleanup period is 90 days, with daily cleanup dependent on WordPress cron and module availability. Developers can change the retention filter, with a minimum of seven days enforced by the implementation. Inform staff whose activity is logged and choose access and retention arrangements suitable for your site.

Maintenance mode presents a holding page with an HTTP 503 response while you work. Confirm which signed-in users can bypass it and test as a signed-out visitor. Check commerce and third-party callbacks before using it on a live shop. A 503 signals temporary unavailability; it cannot guarantee that search rankings are unaffected.

Turn maintenance mode off when work is complete and test an uncached public URL. If you are troubleshooting a cached holding page, clear the relevant cache before changing unrelated settings.

Pro

Measure plugin impact

Plugin impact helps compare time, database work and page weight associated with installed plugins. Measurements depend on the tested page, cache state, hosting load and active configuration. A single run is not proof that a plugin is defective or the main cause of poor performance.

Use a staging copy and a representative page. Record the baseline, repeat comparable measurements and investigate large differences with the plugin's own documentation or a profiler. Keep required commerce, security and integration plugins in mind before deciding what to disable.

A faster dashboard does not automatically mean a faster public website. Check both. Reports may describe the installed plugin stack, so treat screenshots and exported findings as site information when sharing them with support.

Free + Pro

Disable, uninstall and retain your content

Deactivating a plugin stops it running. Deleting it invokes its uninstall behaviour. Corevum keeps its settings and data by default so you can reinstall. The Workspace settings option for removing Corevum data on deletion changes that behaviour and should only be enabled after you have exported what you need.

With removal enabled, deleting Free removes Corevum configuration, user preferences, form definitions and entries, and media-folder organisation. Ordinary posts, pages, custom post type posts, attachments and users remain. Custom type definitions and field-group definitions can disappear while their content or values remain, so arrange equivalent definitions before relying on that content elsewhere.

Pro follows the same removal preference for its own licence and configuration records and its activity, redirect and missing-page tables. If you intend to remove both with cleanup enabled, delete Pro first while Free's removal setting still exists, then delete Free. Deactivate the licence before uninstalling if you need to release its remote activation slot.

Do not assume uninstall restores every operational change made through the plugin. Role/capability changes, theme choices, published content and changes made through native WordPress screens should be reviewed separately. Backups and exported files have their own retention lifecycle.

Free + Pro

Troubleshooting checklist

A blank workspace usually needs the browser's error and network information plus the WordPress/PHP log. Check that the plugin's built assets are present, the WordPress REST API is reachable for your signed-in user, and a security or caching plugin is not blocking admin requests. Do not share authentication cookies or full request headers in a public report.

If Pro remains locked, confirm both plugin versions, licence activation, the enabled module and any required companion plugin. Check server time, outbound HTTPS access and WordPress cron. If the licence service is unavailable, retry after resolving connectivity rather than repeatedly deleting a previously valid activation.

If a product, ACF field or plugin option is missing, open the same item in Classic WordPress. If it is missing there too, inspect that plugin's configuration and permissions. If it works only in classic, report the exact native URL and reproduction steps to Corevum support.

For unexpected layout or stale content, reload after clearing the relevant cache and compare in a private browser. A change that only fails on one device may involve saved local preferences or extensions. Keep a backup before disabling plugins to isolate a conflict.

1. Record WordPress, PHP, Corevum Free, Corevum Pro and relevant companion-plugin versions.
2. Describe what you expected, what happened and the shortest steps to reproduce it.
3. Repeat on staging and compare with Classic WordPress where possible.
4. Send a redacted screenshot and relevant error message to info@dawsony.com.
5. Never send passwords, payment details, authentication cookies or licence keys in a public report.

Free + Pro

Privacy, terms and support

Corevum Free does not include a Dawsony telemetry service or require a licence-server connection. Website owners remain responsible for the personal data they collect in forms, content, custom fields and logs, and for services they choose to enable. WordPress updates, Gravatar, configured email providers and administrator-added scripts have their own network behaviour.

Corevum Pro uses Dawsony for licence activation, validation, deactivation and authorised updates. The Corevum privacy page explains the fields sent and the distinction between data held on your website and data processed by Dawsony. Our general privacy policy covers website accounts, payments, downloads and support.

For product help, contact info@dawsony.com. For a security issue, report it privately with enough detail to reproduce the problem and avoid publishing credentials or exploit details before a fix is available. The software's GPL licence and the paid subscription terms describe different rights: site limits apply to paid service entitlements, not a replacement for the open-source licence.

Free

Protect unsaved work

Forms, post types, taxonomies, field groups, workspace preferences, performance switches and code settings warn before discarding changed values. Menu and role editors also protect changes. Native WordPress editors retain their own save and revision controls. These warnings do not create backups or autosave custom form definitions.

Choosing Cancel keeps you on the screen with your edits. Choosing Discard leaves your saved work unchanged. Closing a field-group or content-type dialog also checks for unsaved changes.

1. Look for the Unsaved changes message in forms and workspace settings.
2. Save successfully before leaving, or explicitly discard changes.

Free

Test notifications and choose entry retention

Open a saved form and choose Confirmation & email. Send test notification uses the saved recipient list, including {admin_email}. Submitted-field recipient placeholders need a real test enquiry instead. Testing is limited to one request per minute per administrator and does not create a form entry.

WordPress accepted means wp_mail accepted the request. It does not confirm delivery. Check every recipient inbox and spam folder and inspect your mail provider if the test does not arrive.

Entry retention is disabled by default. Choose 30, 90, 180 or 365 days only after exporting anything you need. Daily WordPress cron permanently removes older entries for that form in batches of up to 1,000, including existing entries, spam and trash. Cleanup pauses when Forms is disabled and resumes when enabled. Busy sites or inactive cron may delay cleanup. Email copies, exports and backups are unaffected.

1. Save the form with fixed recipient addresses or {admin_email}.
2. Send a test notification and verify its arrival yourself.
3. Choose the appropriate entry retention period, review the deletion implications and save.

Free

Compatibility and support report

Workspace settings includes Review support report. The report is generated locally and contains Corevum, WordPress and PHP versions, plugin and theme names, module states, the last Site Health counts and selected diagnostic flags.

It excludes licence keys, user details, site URLs, filesystem paths, database credentials and raw error logs. Plugin and theme names still reveal your configuration, so review before sharing. Nothing is sent automatically. A report is a diagnostic snapshot, not a promise that all listed plugins are compatible.

1. Open Workspace settings and select Review support report.
2. Review the JSON and download it if needed.
3. Send it with a redacted description, expected behaviour and steps to reproduce the issue.

Pro

Client help centre

Enable Client help centre in Modules. Administrators configure its title, introduction, support email and phone, plain-text instructions and up to twelve guide, video or support links in Workspace settings.

Website help appears in the sidebar for signed-in users who can read the workspace. Client profiles and menu choices may hide the destination. Videos open their provider in a new tab only after clicking; there are no automatic third-party embeds. Do not include passwords or private credentials in instructions.

1. Enable the Client help centre module.
2. Write clear instructions for this particular website and add useful links.
3. Save Workspace settings, open Website help and test each link as your client role.

Pro

Agency setup packs

Agency setup packs extend the existing presets with safe module choices, saved branding, client help, workspace visibility and menu labels, ordering and role visibility. Export a saved pack in Workspace settings. Existing schema 1 presets can still be imported; new exports use schema 2.

Import shows server-validated before and after values and warnings for unavailable modules. Nothing changes until Apply setup pack. Missing destinations and roles are filtered to the current site. Configured help links remain links to their original destination and should be reviewed for the new client.

Packs exclude passwords, licence keys, attachment IDs, uninstall choices, role capabilities, code snippets and maintenance or performance switches. Upload the new site logo separately. They do not install plugins or transfer content. Menu customisations are filtered to destinations installed on the receiving site, and unknown roles are removed. Files must be smaller than 500 KB. Settings for unavailable or disabled modules are skipped, and runtime permissions remain enforced.

1. Save the source workspace preferences before exporting.
2. Import the JSON file on the target site and review every change and warning.
3. Apply the pack and reload so the selected modules load.
4. Set site-specific logos and check the client experience using a separate test account.

Pro

Publishing calendar

Enable Publishing calendar in Modules. Choose a month and content type to see published and scheduled content, using the website timezone. Drafts and pending-review items appear below the calendar until scheduled in their native editor.

Missed schedules show content whose scheduled date has passed but whose status remains scheduled. Check WordPress cron and open the editor before deciding to publish or change its date. The calendar does not silently publish or reschedule anything.

The overview supports editable post types available through the REST API and excludes media, products and store records. Each item requires edit permission; authors see only their own items. Up to 200 items per type are shown in each section, with a notice when a limit is reached. On phones the month becomes a compact list of days with content.

1. Choose Publishing calendar and set the month and content type.
2. Open any item to use the normal editor, scheduling controls, fields and revisions.
3. Review the draft queue and investigate missed schedules before changing publication.