[C2.1] Plugin: BuyCourse: Manage service relation with courses

[NicoDucou]

In the Buy course plugin you can configure services that give new benefits such as a new maximum number of course, a new hosting limit per course or a document quota.
First we have to change the setting "Maximum courses" in the granted benefits, to name it number of course with these benefits.
To know for which course the user wants those benefits to apply the process will be as follow :

• In the administration of the buy course plugin on the service creation and edition page add a setting "Display service on course creation page" that can be true or false
• On the course creation page, if the buy course plugin is available and at least 1 service has the setting "Display service on course creation page" with the value true then show a selector to define the type of course to create with a first bloc for standard course indicating the global setting of the platform for maximum number of course, document quota and maximum student per course and then 1 bloc per service in the buy course plugin that have the setting "Display service on course creation page" on true and for those a link to go to buy this service. The service option is in grey and can not be selected if the user have already used its number of courses available. That is to say that the user have already created the maximum number of courses with those benefits.
• When selecting a service then the settings of the course created are adapted to the value of the service selected and in the buy course plugin we create a registry in a new table service_rel_course_rel_user to know that a course is related to this specific service for this user. This allow to know the number of course the user has with this benefits.
• On the course creation page the logic to know if a user can still create a course is a bit different. We always show the page but we put in grey the services if they are already reached and we block the course creation if the platform limit is reach and no service is available.

Extra
Add a command in Chamilo that checks if a service is finished (That means the duration of the service is over and the user has not payed for a new period). If so, for all the course associated with this service for this user set the accessibility setting of those course to closed. If the service is over since more than a month and the course is closed then set all the course accessibility setting to hidden.

[christianbeeznest]

Implemented in #8374 and merged into 2.1 master.

This implementation introduces the complete BuyCourses service-to-course flow for teacher service subscriptions.

Functional flow implemented:

1. An admin can configure services with course-related benefits:

   • number of courses with these benefits;
   • hosting/users limit per course;
   • document quota per course;
   • whether the service should be displayed on the course creation page.

2. A teacher can buy one or more services. Each purchased service is stored as a service sale, with recurring payment metadata when the purchase is recurrent.

3. On the course creation page, the teacher now sees:

   • the standard course option;
   • one option per BuyCourses service configured with “Display service on course creation page”.

4. A service option can only be selected if:

   • the teacher has an active purchase for that service;
   • the service is still valid;
   • the teacher has not reached the number of courses allowed with those benefits.

5. When a course is created with a service, BuyCourses creates a relation between:

   • the service sale;
   • the service;
   • the course;
   • the user.

   This is stored in the new plugin_buycourses_subscription_course table, which is the implemented equivalent of the requested service_rel_course_rel_user concept.

6. The course receives a snapshot of the selected service benefits in context_json, for example:

   • max_courses_with_benefits;
   • hosting_limit;
   • document_quota_mb;
   • subscription dates;
   • recurring profile/subscription reference.

7. The selected benefits only affect newly-created courses linked to that service. Existing courses are not modified.

8. The course creation page keeps the standard course option available, but service options are disabled when the teacher has reached the service-specific limit.

9. A Symfony command was added to process the lifecycle of recurring service subscriptions:

   php bin/console chamilo:buycourses:process-recurring-subscriptions

   The command:

   • detects expired recurring service sales;
   • marks the recurring sale as suspended;
   • closes courses created under that service;
   • hides courses that have remained closed past the configured threshold;
   • reactivates closed/hidden courses when the recurring service becomes active again.

Database changes added:

• plugin_buycourses_services.display_on_course_creation_page
• plugin_buycourses_services.subscription_behavior_json
• plugin_buycourses_services.stripe_price_id
• recurring metadata fields in plugin_buycourses_service_sale
• VAT/buyer evidence fields in plugin_buycourses_service_sale
• plugin_buycourses_service_rel_extra_field
• plugin_buycourses_frozen_enrollment
• plugin_buycourses_subscription_course

Related issues:

• Related to [C2.1] BuyCourse plugin: Add subscriptions management #8351 because the service lifecycle depends on recurring subscriptions and the command handles expired/renewed subscriptions.
• Related to BuyCourses: Record buyer's location #3840 only from the paid-access perspective: benefits and course access changes are applied only after a confirmed service purchase. This does not claim to fully close the historical direct course-registration bypass scenario described there.

Current verification on testing21:

• Stripe test recurring service purchase works.
• VAT B2C total was applied correctly.
• The service appears in My Services as active.
• Receipt/invoice download works.
• Course creation shows the service options.
• Courses created with a purchased service are registered in plugin_buycourses_subscription_course.
• The course counter for the service works.
• The command closes courses when the service is expired.
• The command reactivates courses when the service becomes active again.

Notes:

• The recurring command must be installed as a cron job for automatic lifecycle processing.
• Stripe requires the webhook endpoint to be configured.
• PayPal sandbox EUR payments require the merchant sandbox account to accept EUR.
• GeoIP evidence requires MaxMind credentials and a public IP.