Sell LifterLMS courses and memberships through WooCommerce.
The main reason some choose to use the LifterLMS WooCommerce integration instead of the native LifterLMS ecommerce system is for one of the following reasons:
The courses or memberships are going to be in an online store with other different kinds of products
You need a WooCommerce payment gateway
You need to have advanced tax rules like VAT that WooCommerce can accommodate
The LifterLMS WooCommerce integration supports WooCommerce Subscriptions if you need to accept recurring payments through WooCommerce.
Please update LifterLMS WooCommerce Extension 2.2.2 to 2.3.0. @Steve
Hi salsamology,
We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.
Please read this topic for more information:
please try we really need this plugin to be updated…
Hi salsamology,
We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.
Please read this topic for more information:
One of the main reason we invested in Festinger is to avoid these expensive plugins and to manage them on client sites. There are few plugins i know that are 100% protected. but this one should be straight forward. Please have a second look.
Please update LifterLMS WooCommerce Extension 2.2.2 to version 2.3.0. @Steve
Can you guys kindly take another look at updating this plugin to 2.3.0 please?
Please update LifterLMS WooCommerce Extension 2.2.2 to 2.4.0. @Steve
Hi salsamology,
We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.
Please read this topic for more information:
@Steve → please check this extension more carefully and update @salsamology if it’s possible to update.