PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

define(‘GF_LICENSE_KEY’.. working?

  1. WordPress 3.0 Multi-Site Enhancement: Now you can pre-populate your license key for multi-site installs. You can pre-define the license key in your wp-config.php file by adding define(‘GF_LICENSE_KEY’,'YOUR_KEY_GOES_HERE’);.

    Well.. after loooong time, i return wordpress development. Firstly i tried to install gravityform @ multi-site but..
    define(‘GF_LICENSE_KEY’,'YOUR_KEY_GOES_HERE’);
    is not worked for me. I tried to add this code after i activated plugin. I tried re-install but still didnt worked.

    Posted 14 years ago on Thursday September 16, 2010 | Permalink
  2. The code works as we have numerous users using it like this so there is something with your implementation. Did you input your license key correctly in the 2nd parameter where it says YOUR_KEY_GOES_HERE? Make sure it was entered 100% correct.

    Also, it only happens on new sites that haven't had Gravity Forms activated on yet. If the site already had Gravity Forms activated at one point, it's not going to fire. It only happens when the database data is initially created.

    Posted 14 years ago on Friday September 17, 2010 | Permalink
  3. Carl,

    old topic, but your comment about not going to fire after the plugin has already been activated is still valid. I have network activated Gravity Forms in a Multi-Site environment and after the activation I've added the define(‘GF_LICENSE_KEY’,'YOUR_KEY_GOES_HERE’); in the wp-config.php. This doesn't work indeed.

    Solution: Deactivate, uninstall, reinstall and the plugin is activated in all sub-sites.

    Posted 12 years ago on Friday October 19, 2012 | Permalink
  4. Thanks for the work around Marcel.

    Posted 12 years ago on Wednesday October 24, 2012 | Permalink

This topic has been resolved and has been closed to new replies.