Access Plan & Pricing Table Template Improvements
- The pricing table template has been split into multiple templates which are now rendered via action hooks. No visual changes have been made but if you’ve customized the template using a template override you’ll want to review the template changes before updating!
- New action hooks are available to modify the rendering of access plans in course / membership pricing tables.
llms_access_plan
: Main hook for outputting an entire access plan within the pricing tablellms_before_access_plan
: Called before main content of access plan. Outputs the “Featured” area of plansllms_acces_plan_content
: Main access plan content. Outputs title, pricing info, restrictions, and descriptionllms_acces_plan_footer
: Called after main content. Outputs trial info and the checkout / enrollment button
-
Added filters to the returns of many of the functions in the
LLMS_Acces_Plan
model. - Minor improvements made to
LLMS_Access_Plan
model
Updates and Enhancements
- Improved handling of empty blank / empty data when adding instructors to courses and memberships
- Added filters to the “Sales Page Content” type options & functions for courses and memberships to allow 3rd parties to define their own type of sales page functionality
- Added filters to the saving of access plan data
- Improved the HTML and added CSS classes to the access plan admin panel html view
Bug Fixes
- Fixes issue causing the “Preview Changes” button on courses to lock the “Update” publishing button which prevents changes from being properly saved.gi
- Fixed issue causing PHP errors when viewing courses / memberships on the admin panel when an instructor user was deleted
- Fixed issue causing PHP notices when viewing course / membership post lists on the admin panel when an instructor user was deleted
- Fixed issue causing PHP warnings to be generated when viewing the user add / edit screen on the admin panel
- Fixed an issue which would cause access plans to never be available to users. This bug didn’t affect any existing installations except if you wrote custom code that called the
LLMS_Access_Plan::is_available_to_user()
method.
Leave a Reply