Batch processing for retroactively enrolling members to courses.#108
Open
andrewlimaza wants to merge 2 commits intostrangerstudios:devfrom
Open
Batch processing for retroactively enrolling members to courses.#108andrewlimaza wants to merge 2 commits intostrangerstudios:devfrom
andrewlimaza wants to merge 2 commits intostrangerstudios:devfrom
Conversation
* FEATURE: Added support for batch enrollment for course integrations that use "enrollment".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This won't re-run batches whenever a member is added to a level programmatically and bypasses any WordPress hooks. This needs a bit more thought, but I am adding this PR for the time being. This is definitely a starting point, and something to think about - a workaround would be to delete post meta "_pmpro_courses_batch_enrollment_levels" for the post types and rerun the scheduled actions (which I think is good enough).
Resolves #72.
How to test the changes in this Pull Request:
Tested with Learndash, other modules are untested but logic looks correct and to be tested before next release.