@javasource & @ampedandy
I see there is a Clone Course option… but as noted above, I swear there was once the ability to assign one lesson to multiple courses.
Since the Course Builder was introduced, I’m starting to feel like a Lesson is TIED to a course… like Parent/Child… 1-to-1 relationship. Is there support for 1-to-many (lesson to courses)… or was this done away with?
If there is this ability… can you direct me to the documentation on how to do this… or kindly answer this here?
I think the using one lesson for all thing was a thing of the past.
It was convenient because, as you say, you could edit that one lesson, and have it show the new info in multiple courses.
LifterLMS has never had the ability to “share” lessons between two courses. The relationship has always been a single lesson related to a single course. Courses have many child lessons and every lesson only has a single parent course.
It is a rigid design. It’s a design that we’ve been hotly criticized about because, fundamentally, it makes sense to be able to share various pieces of content across multiple courses. However, I wasn’t so smart as to foresee this as a need many years ago when we developed version 1 of LifterLMS and while I have had lots of users bug me to build “fix” this “bug” I haven’t been able to overcome the architectural flaws in LifterLMS that force this rigid 1 to 1 relationship.
Duplicating content is not ideal. I know. It’s a bandaid for this issue. However, it’s not a simple “fix” to rebuild our design and architecture to accommodate this need.
So for now duplicating lessons is the best feature / option we have to offer if you want to reuse lessons between courses.
Outside of Course Builder I created an orphaned lesson. It’s here I guess that I can copy other EXISTING LESSON content… and then ATTACH it to a CUSTOM Course…
Is this the only way?
Also, how do I DETACH an existing lesson from a Course without deleting it? We have a few lessons we want to move out of one course and put into another. Is the solution the same as above? (Copy content into new orphaned lesson and then drop it into new/existing course)
You can “detach” a lesson from a course and then “attach” it to another course. Use the “broken link” icon on the lesson in the course builder to detach it.
Then use the “Add Existing Lesson” and search for that lesson.
A lesson that is “orphaned” doesn’t have a parent lesson and will simply be attached. A lesson that does have a parent will be duplicated. You’ll see the icons next to the lesson when you search will be either a Paperclip (for attaching) or two pieces of paper stacked on top of each other (for copying). The text says attach or clone respectively.
Btw… If I try to use the Add Existing Lesson from the Course Builder, none of the content is loaded in the new Cloned version…?
Running the most current LifterLMS version as well as WordPress…
Any ideas?
I think I figured it out. We are using Unyson’s Visual Page Builder and have used their Templates section to make it easier to have a consistent look/feel for each course/lesson.
Apparently, LifterLMS won’t apply template content across clones.
I tried it with Brizy, and the clone operation worked fine. I’ll just need to create a whole new series of Lesson templates via Brizy. Ughhh…
Unless you know of a way to hook VPB content across cloned lessons…
The way our cloning works it copies all custom postmeta data and applies it to the new cloned version. I haven’t ever encountered this page builder in question before but with Beaver Builder, Divi’s page builder, and Elementor all the page builder data is stored in the posts postmeta data and during a clone it all is applied correctly to the new copy.
My guess is that this page builder doesn’t store data on the postmeta table — maybe it uses a custom table? — in which case LifterLMS won’t be aware (has no way of being aware) of this content.
There’s two ways to handle this: work with the developers to add support for LifterLMS course/lesson duplication or submit a feature request for us to add support: https://lifterlms.com/feature-request
Sorry you’re having issues here. I know there’s room for us to improve (and we will) but as of right now you’ll have to make due with the aforementioned limitations.
Let me know if you have any other questions.
