Activating your License

Last updated on 2023-07-26 14:55:46

Activating your License

Now you’re ready to register and activate your license.

  1. Navigate to the License Manager,
    • Navigate to (one of) your Daan.dev plugin’s (e.g. CAOS or OMGF) configuration screen and click the newly added Manage License tab.

      Next to the  Help tab of your Daan.dev plugin’s configuration screen, you’ll notice the newly added Manage License tab.

      Can't find the Manage License tab? Please make sure both the base (free) plugin and the premium plugin are both installed. E.g. OMGF Pro needs OMGF to run properly, and OMGF Pro needs to be installed separately. The installation page offers a full rundown on how to install my premium plugins.

  2. Enter your license key in the input field next to the name of purchased plugin, e.g. CAOS Pro or OMGF Pro.
  3. Click Activate Licenses.

Not getting a Success Message?

No worries. We’ll figure it out. Contact me and include the full error message in your message.

Activating your License using WP CLI

In v1.13.0 (released on July 26th, 2023 in all my plugins) of the license manager I've included WP CLI support.

This version is included with:

  • OMGF Pro v3.8.3
  • CAOS Pro v2.5.4
  • OMGF Additional Fonts v1.3.3

For those of you managing a lot of sites (Agency and Ultimate license holders) this allows you to automate plugin installation (using wp plugin activate ) and license activation. Here's how it works:

Listing installed Daan.dev plugins

To activate your license, you'll need a license key (provided to you in the checkout success screen, by email and in your account area) and the ID by which the plugin is identified in the license manager system.

This ID can be retrieved by running the following WP CLI command, without any additional parameters:

wp daan list_plugins

This command will list all installed Daan.dev plugins on your system, along with their internal IDs.

Activating your Daan.dev license using WP CLI

Once you've retrieved the internal ID, the rest is a breeze.

Simply run the following command to activate your license key using WP CLI:

wp daan activate --key="your license_key" --id="internal_id"

You might've guessed that your_license_key and internal_id need to be replaced with actual values, e.g.

If successfull, the output will look something like this:

Licence(s) Failed to Validate

My plugins include a license manager, which encrypts your license keys before storing them into your database. This is to ensure they never end up in anyone's hands besides yours. For encryption two random strings are generated. To limit the risk of a malicious actor finding both: one is stored in the database and the other is stored in WordPress' wp-config.php file.

The licenses are used to check for updates. If for some reason decrypting the license fails, the license manager will display an error in WordPress' admin area:

Required Encryption Key(s) are Missing

To fix this error, follow the on-screen instructions:

  1. Navigate to the Manage Licenses page using the displayed link,
  2. At the bottom of that page you'll notice a button, pulsing a few times, which says Install Missing Encryption Key.
  3. Click on this link and wait for the page to reload.

After the page has reloaded, both the button and the error message should no longer be displayed.

If it doesn't, then it might be your wp-config.php file is locked for editing. This means you'll have to make the modifications yourself:

  1. Navigate to the wp-config.php file stored in the root of your WordPress install.

    Please note that in some installs the wp-config.php is located elsewhere for improved security, usually one directory up from the WordPress install root.

    Example: the German hosting provider Raidboxes, allows you to edit the wp-config.php file from within the server administration area: raidboxes.io > Your Box > Settings > Wordpress > wp-config.php.

    Some hosting providers (like WP Engine's FlyWheel) don't allow access to the wp-config.php file. In this case you'll need to contact them and ask them to make the proposed changes.

  2. Verify that there's no line near the top of the wp-config.php file, containing the string DAAN_LICENSE_ENC_KEY.

    If it is and you're getting the error mentioned above, make sure that there's not another wp-config.php file in use elsewehere. Lost? Contact me

  3. Generate a random encryption key, by clicking here.
  4. Enter the following code, right before this line: "/* That's all, stop editing! Happy publishing. */"
    define('DAAN_LICENSE_ENC_KEY', 'YOUR_ENCRYPTION_KEY');
  5. Replace YOUR_ENCRYPTION_KEY with the string you generated, so it'll look something like this:
    define('DAAN_LICENSE_ENC_KEY', 'psg9LRaDZw2LGnwZ5cKx4OHnF0pcEMLeqSX3DGnVAz3I8F5Cv9lv9p8Sn49Ru3NL');

After this you can savely (re-)enter your license keys.

Still getting the "Required Encryption Keys are Missing" error message?

If you're still getting the required encryption keys are missing error, after adding the DAAN_LICENSE_ENC_KEY constant to the wp-config.php file, then this usually means that your server has implemented increased security by storing the wp-config.php file one directory higher.

Check one level up from your WP installation root. Located the wp-config.php file? Great! Try renaming the wp-config.php you edited earlier (located inside your WordPress installation root) and see if your site still loads properly:

  • If it doesn't, rename the file back to wp-config.php and contact me.
  • If it does, then that file isn't used by WordPress and can safely be deleted. After deleting the file, my license manager will automatically pick up the one stored one level higher and it should be able to store the DAAN_LICENSE_ENC_KEY constant to provide encryption for your license key.

Encryption Key has Changed

In the unusual event that the encryption key has been changed or removed, the error above will be displayed. Without the encryption key, the license keys can't be restored. The only way to resolve this is to re-enter your license keys.

Shopping Cart
  • Your cart is empty.