System requirements
WordPress, PHP, database and server requirements for Authority and Access.
These are the declared minimums the products are written against. If you plan to run at the minimum versions, test on staging first.
| Item | Requirement |
|---|---|
| WordPress | 6.5 or newer |
| Permalinks | “Post name” (/%postname%/). Plain permalinks are not supported. |
| PHP | 8.1 or newer, with the sodium, mbstring, json, curl and zip extensions |
| Database | MySQL 8, or MariaDB 10.5 or newer |
| Upload limit | upload_max_filesize and post_max_size of at least 8 MB — the theme file contains the components |
| HTTPS | Strongly recommended for the site URL |
Server configuration
- Outbound HTTPS from the web server to the WagerThemes licence service, and to any AI or research provider you choose to enable. Without it the product cannot be activated and cannot update.
- A real system cron that runs WordPress scheduled tasks every minute, with
DISABLE_WP_CRONset inwp-config.php. The licence is re-validated twice a day. - Unique
AUTH_KEYandSECURE_AUTH_KEYinwp-config.php. They protect the stored licence token and provider keys; changing them later means re-activating the licence and re-entering API keys. - File access: WordPress must be able to write to
wp-content/plugins/for the one-click component installer. Otherwise the setup screen points you to manual upload.
* * * * * cd /path/to/wordpress && wp cron event run --due-now >/dev/null 2>&1define( 'DISABLE_WP_CRON', true );Optional
- A persistent object cache (Redis or Memcached) is picked up automatically. It is not required.
- Full-page caches and CDNs are supported. Exclude
/go/*,/wp-json/*,/wp-admin/*, search requests and logged-in users from the cache. - Production servers never need Node.js or Composer.