We’ve just released a new version of Sensei that changes the name of the plugin to Sensei with WooCommerce Paid Courses.
You may see a strange version number (2.0.1.1.0.0) when prompted to update. This is due to the fact that Sensei with WooCommerce Paid Courses is a bundle of the free version of Sensei LMS that exists on WordPress.org, and the WooCommerce Paid Courses extension that enables selling courses with WooCommerce.
After updating, you will see Sensei with WooCommerce Paid Courses listed on the Plugins page:
If you currently have a valid Sensei license for your site, nothing changes with the release of Sensei with WooCommerce Paid Courses. Your existing plugin will continue to function as before, and you’ll still receive updates and support.
You can read more about why we made this change here.
¿Qué contiene esta versión?
Here are the highlights of the release:
- The new minimum required version of PHP is 5.6. If you’re not sure which version of PHP your site is running, you may find the How to Check Your WordPress Site’s PHP Version section of this article helpful. You can also read more about updating PHP on WordPress.org.
- La nueva versión mínima requerida de WooCommerce es la 3.0.
- The Access Permissions setting now controls only lesson content, not lesson and course content. Always displaying the content on the single course page is an opportunity to further promote a course and encourage user enrolment.
- Cuando Sensei se activa por primera vez, aparece una ventana emergente que le pide que se una a nuestra lista de correo. Esta ventana emergente solo aparecerá en los sitios en los que nunca se haya instalado Sensei.
- We added a new Sensei LMS extensions page available from the Sensei LMS > Extensions menu.
You can read more about what else is in this release, including template file changes and deprecations, here and here.
Head over to Dashboard → Updates to update Sensei from within WordPress.
Nota: Aunque hemos probado a fondo esta versión, siempre es posible que hayamos pasado algo por alto. Le recomendamos que pruebe la actualización en un sitio de prueba antes de actualizar su sitio activo.
