LifterLMS

Make

The Official Blog for LifterLMS Contributors

  • LifterLMS Stripe Version 4.4.1






    • Added compatibility to allow definition of API credentials in constants as opposed to saving them to the database. See our docs for information on how this works: https://lifterlms.com/docs/lifterlms-stripe/#keys


    Read more: LifterLMS Stripe Version 4.4.1

  • LifterLMS MailChimp Version 3.1.2

    + Added an action which fires when user consent is saved.
    + Fixed an issue causing an error when saving API credentials for the first time.
    + Fixed an issue preventing subscriptions from being created when consent is disabled via the `llms_mc_enable_consent` hook.

    Read more: LifterLMS MailChimp Version 3.1.2

  • LifterLMS Version 3.30.2

    • Added new filter to allow 3rd parties to determine if a LLMS_Post_Model field should be added to the custom array when converting the post to an array.
    • Added hooks and filters to the LLMS_Generator class to allow 3rd parties to easily generate content during course clone and import operations.
    • Fixed an issue causing all available courses to display when the [lifterlms_courses] shortcode is used with the “mine” parameter and the current user viewing the shortcode is not enrolled in any courses.
    • Fixed a PHP undefined variable warning present on the payment confirmation screen.
    Read more: LifterLMS Version 3.30.2

  • LifterLMS Assignments Version 1.1.1

    • Add handlers to handle LifterLMS duplicate assignments during when importing and cloning courses.
    Read more: LifterLMS Assignments Version 1.1.1

  • Working Group Session 3: Merge Codes

    The LifterLMS Working Group will be meeting on April 17, 2019, 9-10am PT for our 3rd session. The focus of this month’s meeting will merge codes.

    LifterLMS currently utilizes merge codes for engagements and notifications. In the future we plan for merge codes can be utilized in all areas of LifterLMS (including LMS and non-LMS posts and pages).

    As the maintainers we’re in the very early phases of clarifying our thinking around how to make merge codes most useful to course creators and before we solidify any plans we look to the working group for feedback and guidance.

    Join us live or leave comments below.

    Check the events calendar for information on the event.

    Read more: Working Group Session 3: Merge Codes

  • LifterLMS PayPal Version 2.0.0-beta.1

    This is the initial (relatively) stable beta release of LifterLMS PayPal 2.0. There are a small number of known issues yet to be resolved. We urge against testing this release in production. Please see our beta testing guide for more information.

    The PayPal “REST” Gateway

    • A completely new version of LifterLMS PayPal utilizing the most recent PayPal APIs and features.
    • Utilizes PayPal Checkout via Smart Payment Buttons.
    • Your API Credentials (Client ID and Client Secret) can be found by following these steps:
    • Look under “REST API apps” at https://developer.paypal.com/docs/classic/lifecycle/sb_credentials/.
    • If testing in Sandbox mode (recommended) you’ll also want to create sandbox buyer and seller accounts: https://developer.paypal.com/docs/classic/lifecycle/sb_about-accounts/
    • The charging and scheduling of recurring payments is managed via the PayPal Billing Agreements API and requires a webhook listener to properly function.
    • This webhook is automatically installed when valid API credentials are added via the gateway’s settings panel.
    • If you’re working on a local development environment you will not be able to receive incoming webhooks and your test subscriptions will never record transactions nor will they cancel enrollment during cancellations from within PayPal.

    The “Legacy” PayPal Gateway

    • Renames the existing NVP/Reference transaction-powered PayPal (1.x) gateway “PayPal (Legacy)”
    • For first-time users this gateway is hidden and not available:
    • To enable the legacy gateway visit LifterLMS -> Status -> Tools & Utilities and click the “Enable Legacy Gateway” button.
    • To disable the legacy gateway repeat the above process clicking “Disable Legacy Gateway” instead.
    • Disabling the legacy gateway will have NO EFFECT on existing one-time payments made via the gateway. However active recurring payments made through reference transactions will be unable to automatically recharge.
    • The gateway itself is marked as deprecated. New users should avoid using the legacy gateway and instead rely on the new REST gateway introduced in this version.

    Deprecated Classes

    The following classes have been marked as deprecated and will be removed from LifterLMS PayPal in the next major release.

    • LLMS_PayPal_Request
    • LLMS_Payment_Gateway_PayPal

    Existing Known Issues

    • It is not possible to refund a transaction via the LifterLMS Order (coming in beta.2).
    • Due to an issue in the PayPal REST API, cancelled billing agreements do not send webhook notifications resulting in students remaining enrolled in the related course / membership when an agreement is cancelled from within PayPal. We’ll be overcomming this by running automatic scheduled checks 24 & 48 hours after payment is due to check on the status of expected recurring payments (coming in beta.2).

    How to help test?

    • Install LifterLMS PayPal in a non-production environment and start using it.
    • If you find any issues or have any questions let us know by opening an issue on the official LifterLMS GitHub, opening a new support request, or posting in #developers on the LifterLMS Slack community.
    • If you install this in production and we will not provide you with emergency or urgent support.
    • Again: Don’t install this in production.
    Read more: LifterLMS PayPal Version 2.0.0-beta.1