TypeRocket v1 Pro users can now upgrade to TypeRocket v5 at their convenience.
( v1 )
Before getting started, be sure your setup supports the TypeRocket Pro system and browser requirements.
To install TypeRocket Pro Plugin for WordPress go to your account and download the plugin zip file. Find the download link at the bottom of your "Purchase Receipt" page.
Note: Do not modify the TypeRocket Pro Plugin files. You would only extend TypeRocket using available hooks and
wp-config.php constants. When the documentation tells you to edit TypeRocket files, those edits should be made to your version of those files.
1. Download & Activate
- Download the latest version of TypeRocket Pro Plugin from your account.
- Upload the plugin in the WordPress admin or unzip the files into your WordPress sites
- Activate the TypeRocket Pro Plugin in WordPress.
- Activate your TypeRocket site license.
From the TypeRocket settings page located under "Settings > TypeRocket" add your site license. Activating your license gives you access to automatic updates.
Your license restricts you to a specific number of activations. You can remove old or current sites form your license in your typerocket.com account.
2. Create Override Folders
Optionally, once you have installed TypeRocket, you may want to override the base configuration. You can do this in two ways; by placing the override folders, with files, in the active theme or the root of your site.
First, access and download the TypeRocket Pro project override folders from GitHub. The override folders include:
Next, place those folders in either:
- The root of your active theme.
- The root of your WordPress installation where your
If you place your files in the root of WordPress (not your active theme) also add the following to your
// Root WordPress customizations define('TR_CORE_CONFIG_PATH', __DIR__ . '/config'); define('TR_ALT_PATH', __DIR__); define('TR_APP_NAMESPACE', 'App'); define('TR_AUTOLOAD_APP', [ 'prefix' => TR_APP_NAMESPACE . '\\', 'folder' => __DIR__. '/app/', ]);
Found a typo? Something is wrong in this documentation? Fork and edit it!