Check system requirements
Check your hosting environment and prepare the services required for the features you plan to use.
On this page
Overview
HelSup requires WordPress 6.2+, PHP 8.0+, and a MySQL/MariaDB database the site already uses. The plugin creates its own tables (your WordPress table prefix followed by helsup_support_).
When to use this
Meeting requirements avoids silent queue failure, missing IMAP, and REST 401 after cookie/nonce issues.
Where to find the controls
Settings → System → System (health) and System Status. Also Tools → Site Health in WordPress.
Who can make these changes
The person installing the plugin (site admin). Agents do not need to check PHP modules.
Before you begin
Optional: PHP IMAP for inbound email; WooCommerce for order context; an AI provider key for Copilot and Chat AI; system cron hitting wp-cron.php.
Follow these steps
- Confirm PHP 8.0+ (php -v).
- Confirm WP 6.2+.
- Open System Status after activation.
- If email inbound is required, enable the IMAP extension.
- Schedule system cron in production; WP-Cron alone is traffic-driven.
Settings reference
System Status reports queue depth, cron last run, REST namespace elegant-support/v1, rewrite/permalink health, and feature flags.
Example workflow
A host without IMAP: Email settings load, but inbound polling cannot run. The UI states IMAP unavailable rather than faking success.
Good practices
Keep object-cache and page-cache plugins from caching wp-admin REST. Exclude /wp-json/elegant-support/.
Important considerations
PHP below 8.0 is unsupported. Do not run on a site where another plugin also claims the same rest namespace.
If something does not work
White screen on activation: enable WP_DEBUG, check for a fatal in another mu-plugin, and confirm autoload paths. REST 404: flush permalinks.