Title: Development License
Last modified: September 27, 2022

---

# Development License

 *  Resolved [SQLGuru](https://wordpress.org/support/users/sqlguru/)
 * (@sqlguru)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/development-license/)
 * Good Day.
 * We have purchased the PRO version of the plugin which we are currently using 
   in our production website.
 * We are currently in the process of re-developing the entire website and we are
   needing to import all the PPPOM settings from the production to dev environment.
   Unfortunately, it seems that the free version (installed in the dev env) does
   not have the option to import settings.
 * Would it be possible to get a temporary API key so that I we can install the 
   PRO version on the dev site. Once we launch the new site, we are happy to use
   the existing API key for our PRO license.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [Stefan Cotitosu](https://wordpress.org/support/users/stefancotitosu/)
 * (@stefancotitosu)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/development-license/#post-16046923)
 * Hi [@sqlguru](https://wordpress.org/support/users/sqlguru/),
 * Thank you for reaching out to us and for using the plugin.
 * Yes, the license key for the premium version can be used temporarily on a staging
   site before configuring the plugin on the production one, then moved there.
 * For more questions about the premium version, feel free to contact the support
   team via the pre-sales form – [https://themeisle.com/contact/](https://themeisle.com/contact/).
 * Have a great day ahead!
 *  Thread Starter [SQLGuru](https://wordpress.org/support/users/sqlguru/)
 * (@sqlguru)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/development-license/#post-16046953)
 * When trying to enter the Production API Key, nothing happens. If I inspect the
   console, I can see an error:
 * VM21986:1 Uncaught SyntaxError: Unexpected token ‘<‘, “<!doctype “… is not valid
   JSON
    at parse (<anonymous>) at Function.<anonymous> (jquery-migrate.min.js?ver
   =3.3.2:2:2469) at e.<computed> [as parseJSON] (jquery-migrate.min.js?ver=3.3.2:
   2:1205) at Object.success (validate.js?ver=6.0.2:10:26) at c (jquery.min.js?ver
   =3.6.0:2:28327) at Object.fireWith [as resolveWith] (jquery.min.js?ver=3.6.0:
   2:29072) at l (jquery.min.js?ver=3.6.0:2:79901) at XMLHttpRequest.<anonymous>(
   jquery.min.js?ver=3.6.0:2:82355)`
 *  Plugin Support [Stefan Cotitosu](https://wordpress.org/support/users/stefancotitosu/)
 * (@stefancotitosu)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/development-license/#post-16047022)
 * Hi [@sqlguru](https://wordpress.org/support/users/sqlguru/),
 * If this is related to the premium version of the plugin, please contact us on
   our website – [https://themeisle.com/contact/](https://themeisle.com/contact/).
 * The forum is dedicated to the free version, therefore, troubleshooting a problem
   related to the pro version on this thread might not be beneficial for other users.
 * Thank you for understanding.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Development License’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce-product-addon/assets/icon-256x256.gif?rev=3186763)
 * [PPOM - Product Addons & Custom Fields for WooCommerce](https://wordpress.org/plugins/woocommerce-product-addon/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-product-addon/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce-product-addon/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce-product-addon/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-product-addon/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce-product-addon/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Stefan Cotitosu](https://wordpress.org/support/users/stefancotitosu/)
 * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/development-license/#post-16047022)
 * Status: resolved