I have a client who offers both In House Training and on-line training. The In House is separate from the online. We need be able to filter Courses by date of training and purchase them on line for the in house training. The way Opigno has implemented In House Training has the date stored with the in House Training entity but the product is attached to the course entity. The two entities connected by the "Course Tools" custom structure (which is not referable back and forth in views) I am trying to figure out whether I want to mess with PHP in a views filter/ Computed field in the Course Entity to hold the dates of the In House Training for that Course or scrap In House Training entirely and create my own entity that is referenced in Course. I am leaning toward scraping the In House Training structure at this point. Does anyone have any insight into this situation?
So you want to charge individual in house lessons and live meetings? Is that it?
Or you have different courses with different ihm and live meetings and you want to sell the courses?Can you explain the use case a bit in more detail? Can you give me an example of the user actions when he pays etc?
I want to charge for