Hi Guys,
I wanted to ask you if there's a way of using Cobalt+Emerald with native features to solve the following e-learning scenario.
I have an e-learning site with:
Type A: Courses
A course has general characteristic about a course, with a description, an image, etc. Nothing special nor restricted. Courses can be added by registered users.
However, there's a relate field (parent type) where users can submit the content in different classes.
Type B: Classes
They contain the course material. They can be of different types (videos, images, html, etc.).
I need Classes to be available (accessed) only to people that buys the course (payment).
What I want?
I want users to pay to access to the course material (classes). However, the fields located at the course level aren't restricted, they contain general information about the course to tease users to buy it.
So, when a users pays, access to classes should be granted.
I tried using "paytoaccess" field at the Course level, but this doesn't let users get into the course. I need them to get into the course to see more details about the course, reviews, rates, comments, etc, and then if they liked they would be able to access classes (if they pay).
So, if there any way of solving this scenario using Cobalt+Emerald? If not, what would you think it would be the most simple solution (even if it means to add some customization or a special field "paytocourse" (e.g)?
I'm currently developing this scenario for one of my clients on localhost, but I plan to upload everything to a server by tomorrow, it would be good to know how to approach this scenario so that I can start working on it.
Thanks for all,
Matias
Hi Guys,
I wanted to ask you if there's a way of using Cobalt+Emerald with native features to solve the following e-learning scenario.
I have an e-learning site with:
Type A: Courses
A course has general characteristic about a course, with a description, an image, etc. Nothing special nor restricted. Courses can be added by registered users.
However, there's a relate field (parent type) where users can submit the content in different classes.
Type B: Classes
They contain the course material. They can be of different types (videos, images, html, etc.).
I need Classes to be available (accessed) only to people that buys the course (payment).
What I want?
I want users to pay to access to the course material (classes). However, the fields located at the course level aren't restricted, they contain general information about the course to tease users to buy it.
So, when a users pays, access to classes should be granted.
I tried using "paytoaccess" field at the Course level, but this doesn't let users get into the course. I need them to get into the course to see more details about the course, reviews, rates, comments, etc, and then if they liked they would be able to access classes (if they pay).
So, if there any way of solving this scenario using Cobalt+Emerald? If not, what would you think it would be the most simple solution (even if it means to add some customization or a special field "paytocourse" (e.g)?
I'm currently developing this scenario for one of my clients on localhost, but I plan to upload everything to a server by tomorrow, it would be good to know how to approach this scenario so that I can start working on it.
Thanks for all,
Matias