It’s Tuesday, and you know what that means – it’s time for some updates!
We are delighted to let everyone utilizing the Learn platform know that we are releasing a series of updates, improvements, and fixes to the platform!
Firstly, we would like to say a HUGE thank you to the 110+ users that opted-in to the Learn beta. Since August 13, 2024, they have been providing us with invaluable feedback on the updates, allowing us to test at scale across thousands of students ahead of this release.
Here’s the list of everything we’ve tackled so far:
Speeding Up Student Access with the Learn Content Release Engine:
The way the system was originally built meant that each time a modification was added (i.e., new upload of students), the system would go through all the students to reapply permission, not just those being added/modified. This worked well when Learn was first launched, but with over 4 million students now on the platform, it needed a re-think!
We fixed this by abandoning the queue method in favor of a new system we call the Learn Content Release Engine. This calculates grants on demand for students when they access a course/module, resulting in instant updates rather than taking hours or days to complete.
Fixing Module and Lesson Counts:
We had heard of issues with students having incorrect module/lesson counts on their profile, as well as in the dashboard from an administrator view. On investigating, we found that this was a database error involving “soft deleted” lessons and modules. We have applied the same proprietary approach used in the Learn Content Release Engine and this allowed us to set better parameters so the counts were rectified.
Fixing Tag Access Issues:
If a module is set up for specific tags, students with the associated tag were not always being granted access to that content. We have identified what was causing the problem and fixed it.
Timed Rules:
During the beta, we discovered it was possible to set a lesson or module to be released based on time. However, without setting a day/week/month/year, this caused a 500 error. We’ve now made it mandatory to select a day/week/month/year for this timed rule to exist, which eliminates the possibility of the error happening again.
Tags and All Students:
In some cases, students weren’t able to see lessons and modules that previously had required tags set after the lesson/module is switched to “all students” – the tags should have always been stored, but not applied. Now, students without those specific tags will be able to see the modules and lessons that are later published to “all students” and the previously required tags will simply be saved in the backend.
Additionally, assigning tags would not always unlock course content – after a deep dive into the code, we were able to fix this issue as well.
Dripping Content to Students:
Learn users identified an issue affecting the queuing and dripping of lesson content to existing students on a course when the content is set to drip out a specific time after the student is part of the course; in some cases, when lesson content is backdated and so the upcoming date/time period has passed.
We’ve implemented a fix that improved the content dripping system for students, which meant updating sequence rules in the code to work more effectively for this specific type of task.
________
As you can see, there are a lot of updates here so if you have any questions, please feel free to reach out!
None of this would be possible without our amazing beta group! This group will remain open as we continue to optimize and add new features.
Meanwhile, we’ve made more improvements across ThriveCart this week, so let’s see what else is new:
Learn: students – before now you were able to see when your students were first enrolled, but your students could sign up to courses at different times and it might not have been easy to tell when they became a student of a specific course. Now, we’ve added the date and time a student enrolled into each course into their student profile, so you can see exactly when they signed up to each course.
Mailerlite – if you set a behavior rule for their product using Mailerlite, it may not have worked properly and attempts to fix the issue may have thrown up an error message. We’ve identified and fixed the issue, so your Mailerlite integrations will now be working properly.
Sub-users – sub-users may have encountered problems saving a product when a Learn course has been set as the fulfillment method, in which the Learn course did not show. We’ve fixed this now and your sub-users can save products as normal.
That’s it for this week! If you have any issues with ThriveCart, please check our help docs for guidance or reach out to support and we’ll be in touch.
We’ll be back soon with more updates for you – until then, keep thriving!
All the best,
The ThriveCart Team
All Rights Reserved