LifterLMS 5.0.0 is scheduled for release in mid-June, 2021. In addition to various bug fixes and improvements, this major release focuses primarily on improving the management and construction of student checkout, enrollment, and registration forms.
As a major release, some backwards incompatible changes have been made to the code base. These changes have been noted in the changelogs and compiled in the Breaking Changes section below.
The following is our target release schedule for LifterLMS version 5.0.0. The dates of these prerelease builds may be adjusted and additional versions may be added. The date of General Public Release may be delayed but will not be released early.
| Wednesday May 19, 2021 | Beta.1 |
| Tuesday May 25, 2021 +6d | Beta.2 |
| Tuesday June 1, 2021 +1w | Beta.3 |
| Tuesday June 8, 2021 +1w | RC.1 |
| Tuesday June 15, 2021 +1w | RC.2 |
| Monday, June 21, 2021 +6d | 5.0.0 General Public Release |
We strive, wherever possible, to remain backwards compatible. Doing so ensures that themes and integration do not have to worry about their code bases being negatively impacted by changes in LifterLMS. However, this also results in a larger code base full of many unused and deprecated functions, classes, and files.
All breaking changes have been noted in the alpha version changelogs and are summarized here:
The locations of some included libraries have been moved. Direct references to any files in these libraries will have to be updated.
libraries/ directory in favor of the vendor/ directory.vendor/deliciousbrains/wp-background-processing directory.The following items have been removed from the codebase:
topModal.js has been removed.LLMS_Quiz::get_lessons() has been removed.LLMS_Controller_Quizzes::take_quiz() has been removed.LLMS_Processor_Table_To_Csv has been removed.LLMS_Processors::includes() has been removed.LLMS_Person_Handler::fill_fields() and LLMS_Person_Handler::insert_data() were removed.The following deprecations have been made and will be removed in a future major update.
LLMS_Person_Handler::get_available_fields() is deprecated in favor of LLMS_Forms::get_form_fields().LLMS_Person_Handler::register() is deprecated, in favor of llms_register_user().LLMS_Person_Handler::sanitize_field() (private method) is deprecated with no replacement.LLMS_Person_Handler::update() is deprecated, in favor of llms_update_user().LLMS_Person_Handler::validate_fields() is deprecated with no replacement.LLMS_Person_Handler::voucher_toggle_script() is deprecated with no replacement.lifterlms_get_user_custom_fields in favor of llms_admin_profile_fieldsllms_usernames_blacklist is deprecated, use llms_usernames_blocklist instead.llms_get_minimum_password_strength() is deprecated with no replacement.lifterlms_registration_generate_username is deprecated in favor of the new method LLMS_Forms::are_usernames_enabled().LifterLMS does not (and will not) maintain multiple forks. We support and maintain a single stable release.
Upon the public release of LifterLMS 5.0.0, all users are encouraged to update to this version. All future updates to LifterLMS will be updates to version 5.0.0.
The prereleases are available publicly to anyone interested in helping the core team root out bugs and issues.
Beta testing is not always fun or easy. The prereleases are considered generally stable but you should still use caution and expect to find some issues.
If you find any issues, please let us know by filing a new bug report or submitting a support request.
If you have general comments or feedback on the beta let us know in the comments below or post a reply in GitHub on our 5.0.0 general feedback issue.
There are three ways to install a prerelease version for evaluation and testing. Please do not install prereleases on production websites!
The changes in this release primarily revolve around building and managing the forms (checkout, enrollment, registration, and user information) that your students see on the front-end of the website, so, start with your forms.
If you nave any 3rd-party integrations or themes installed on your site, you should check if developer has tested compatibility with LifterLMS 5.0.0 and, if they haven’t, ask them to do so as soon as possible to ensure there’s no issues when 5.0.0 is released to the stable channel.
If you have any custom code on your site that is meant to programmatically add custom fields or modify your site’s forms, you should test to ensure this code continues to work as expected. LifterLMS 5.0.0 will still allow for programmatic modification of user forms but the new functionality aims to render code like this useless since much of what you may have wanted to modify can now be done in the block editor without any code.
If you encounter any problems you should let your developer know and if you get stuck, file a new bug report or submit a support request and we’ll point you in the right direction.
If you maintain a LifterLMS theme, plugin, or integration we need your help!
Please install the latest prerelease version and test your code against ours. If you find any issues along the way let us know by reporting an issue in GitHub.
After testing your integration please let us know by commenting on our 5.0.0 feedback issue.
If you’re a member of the LifterLMS Experts program please collaborate with us during this beta period and help us ensure the transition to version 5.0.0 is as smooth as possible for your clients.
We’d like you to, at the very least, install and test the beta in your own testing environment.
As an expert we expect that you have a few LifterLMS clients, possibly with custom templates and feature plugins. If your clients (and contracts) allow, please test (or help your clients test) the beta in a safe testing or staging environment.
If you encounter any issues or run tests and find that everything goes well, please let us know by posting in GitHub or by directly emailing your contact at LifterLMS.
lifterlms_get_user_custom_fields in favor of llms_admin_profile_fieldsblock_categories.