Bug Fixes
- Fixed an issue with emojis in essays by not running autosave on completed essays.
- Fixed issue causing escape characters to be added when saving essay assignment submissions.
<header>
and <footer>
in favor of default <div>
tags. #2281.wp-block-column
element. #2134scroll-behavior: smooth
on checkout screen to address form element validity checking issues on Chromium-based browsers. #2206LLMS_Controller_Orders::switch_payment_source()
in favor of LLMS_Controller_Checkout::switch_payment_source()
.lifterlms_update_option_{$type}
action in favor of the llms_update_option_{$type}
filter.LLMS_Controller_Orders::confirm_pending_order()
is deprecated in favor of LLMS_Controller_Checkout::confirm_pending_order()
.LLMS_Controller_Orders::create_pending_order()
is deprecated in favor of LLMS_Controller_Checkout::create_pending_order()
.LLMS_Controller_Orders::switch_payment_source()
is deprecated in favor of LLMS_Controller_Checkout::switch_payment_source()
.window.LLMS.Spinner
functions is deprecated. Use JS Elements
or selection strings parseable by document.querySelector()
instead.llms_{$method}_title
in favor of llms_{$method}_refund_title
.llms_get_dashicon_link()
, intended to enable the addition of external resource helper links to settings field descriptions.LLMS_Student
object can be instantiated as an empty object and bypass current user autoloading. In the future this may affect integrations using the lifterlms_new_pending_order
action hook which will receive an “empty” student object during order setup by gateways utilizing new AJAX-powered checkout endpoints.llms_gateway_{$this->id}_logging_enabled
, which will allow force enabling/disabling of gateway logging functions.add_secure_string()
allowing developers to add secure strings during runtime without the necessity of registering the strings using filters.llms_is_option_secure()
for determining if an “secured” option is defined in a “secure” manner.modify_recurring_payments
. #2176$encode
to optionally get a raw (not encoded) URL. – $querystring_only
to optionally get only the redirect URL if set via NPUT_GET variable.$querystring_only
to the filter hook llms_plan_get_checkout_redirection
.after_html
for additional field types which support desc
..llms-spinning
and .llms-spinner
elements is no longer loaded as part of the lifterlms.css
and admin.css
files, instead it is loaded dynamically when window.LLMS.Spinner
functions are called. In some cases CSS overrides to these elements which relied on CSS rule load order may no longer successfully override the default CSS rules. These overrides may need to be updated to have more specific selectors in order to ensure the overrides are retained.window.LLMS.Spinner
, has been converted to a module accessible from the same variable.window.LLMS.Spinner
methods now accept JS Elements and selector strings parseable by document.querySelector()
in addition to jQuery selections.llms_transaction_can_be_refunded
enabling custom refund restrictions to be applied to a transaction.add_filter( 'llms_use_google_webfonts', '__return_true' );
. #2189@woocommerce/action-scheduler
, to version 3.5.2.During the month of October, LifterLMS will be celebrating open source with our fifth annual Hacktoberfest event: LifterLMS Contributor Month.
Hacktoberfest is a month-long open source community event organized by DigitalOcean.
LifterLMS will be participating in Hacktoberfest as a project maintainer. We encourage anyone to submit pull requests to any of the LifterLMS codebases found on GitHub.
Contributing to open source projects is a great way to learn, practice your skills, meet new people, have your voice heard within a community, and build a public reputation you can take with you outside the project.
Anyone with a GitHub account can submit a pull request. If you don’t have one, you can sign up for free.
You don’t have to be a developer or coder to contribute. LifterLMS will accept contributions from QA testers, user experience and interface designers, documenters, and more! If you’re interested in participating but you don’t know how, get in touch with us and we’ll be happy to get you pointed in the right direction based on your unique set of skills and talents.
Whether you’re a designer, developer, want to help with documentation, or something else entirely we have a task for you!
If you’re looking to write or improve new code, tests, or documentation, head over to our the LifterLMS GitHub repo and start looking through our existing issues. We’re using the special hacktoberfest
tag for issues we feel would be ideal for first-time or new contributors to tackle during this event. You can view all these issues here. You could also check out our good first time contributor issues here.
If you plan to work on an issue please comment and let us know. This will help prevent collisions or duplicate efforts with other contributors.
Please review our contributor’s guidelines and ensure you’re adhering to our coding and documentation standards before submitting a PR!
You may also want to familiarize yourself with how to write and submit pull requests, and DigitalOcean has a great guide you can review here.
Finally, make sure you sign up for the official Hacktoberfest event so your eligible to win an official event prizes!
In addition to the satisfaction inherent in contributing to an open source project, we’ll be awarding prizes to anyone who contributes to LifterLMS during the month of October.
Every accepted pull request will provide you with an entry into a drawing for a free LifterLMS add-on license of your choice valued up to $360.
Anyone who submits three or more accepted pull requests will receive a LifterLMS t-shirt, hat, or mug (your choice).
All pull requests will be reviewed by the LifterLMS team by October 31, 2022. Only accepted pull requests count towards your contribution count.
During the month of October we have several events to help support anyone looking to contribute:
Office Hours
In addition to our weekly Monday Developer Office Hours held in Slack in the #general
channel, we’ll also be hosting short dev chats throughout the month. If you can’t make a scheduled dev chat just pop your question and one of our team members will get back to you when we’re available.
These informal chats are a great opportunity to interact with LifterLMS core developers and other contributors.
If you have any questions about any contributions you want to make, if you’re just getting started, or if you want to just say hello and keep us company, these dev chats are for you (and you don’t have to be a developer to join).
scroll-behavior: smooth
on checkout screen to address form element validity checking issues on Chromium-based browsers. #2206LLMS_Controller_Orders::switch_payment_source()
in favor of LLMS_Controller_Checkout::switch_payment_source()
.lifterlms_update_option_{$type}
action in favor of the llms_update_option_{$type}
filter.LLMS_Controller_Orders::confirm_pending_order()
is deprecated in favor of LLMS_Controller_Checkout::confirm_pending_order()
.LLMS_Controller_Orders::create_pending_order()
is deprecated in favor of LLMS_Controller_Checkout::create_pending_order()
.LLMS_Controller_Orders::switch_payment_source()
is deprecated in favor of LLMS_Controller_Checkout::switch_payment_source()
.window.LLMS.Spinner
functions is deprecated. Use JS Elements
or selection strings parseable by document.querySelector()
instead.llms_{$method}_title
in favor of llms_{$method}_refund_title
.llms_get_dashicon_link()
, intended to enable the addition of external resource helper links to settings field descriptions.LLMS_Student
object can be instantiated as an empty object and bypass current user autoloading. In the future this may affect integrations using the lifterlms_new_pending_order
action hook which will receive an “empty” student object during order setup by gateways utilizing new AJAX-powered checkout endpoints.llms_gateway_{$this->id}_logging_enabled
, which will allow force enabling/disabling of gateway logging functions.add_secure_string()
allowing developers to add secure strings during runtime without the necessity of registering the strings using filters.llms_is_option_secure()
for determining if an “secured” option is defined in a “secure” manner.modify_recurring_payments
. #2176$encode
to optionally get a raw (not encoded) URL. – $querystring_only
to optionally get only the redirect URL if set via NPUT_GET variable.$querystring_only
to the filter hook llms_plan_get_checkout_redirection
.after_html
for additional field types which support desc
..llms-spinning
and .llms-spinner
elements is no longer loaded as part of the lifterlms.css
and admin.css
files, instead it is loaded dynamically when window.LLMS.Spinner
functions are called. In some cases CSS overrides to these elements which relied on CSS rule load order may no longer successfully override the default CSS rules. These overrides may need to be updated to have more specific selectors in order to ensure the overrides are retained.window.LLMS.Spinner
, has been converted to a module accessible from the same variable.window.LLMS.Spinner
methods now accept JS Elements and selector strings parseable by document.querySelector()
in addition to jQuery selections.llms_transaction_can_be_refunded
enabling custom refund restrictions to be applied to a transaction.woocommerce/action-scheduler
to version 3.5.1.