• There are lots of inconsistency in the plugin codes

    1. Email
    – echo ‘Password : 1Admin@23 <br><br>’;, this is WRONG, in the file class-dc-woodle-enrollment.php line #190, the password was made generated and thus, this would lead to a password mismatch.
    – Why? the password sent to Moodle was hash generated, yet, in fact, in the Email, you’re telling the user to use the 1Admin@23.
    2. The same file in Step #1, the hook added was do_action( ‘woodle_after_create_moodle_user’, $user_data );, but it was never used in the email.
    – Instead, it uses the email template with static password field in it.
    3. File dc-woodle-functions.php line #392, again, another code inconsistency.
    ..

    BUG
    1. In the email, the shortcode wasn’t formatted correctly, line #14 in new-enrollment.php file
    2. It won’t create a user in the Moodle area, it returned errocode.
    ..

    The plugin is a great foundation, and thanks for it.

    • This topic was modified 4 years, 9 months ago by Ryan Sutana.
Viewing 3 replies - 1 through 3 (of 3 total)
  • @ryscript

    All the issues have been resolved with the latest update. We also have added the bulk purchase feature with it. The username and password will also be emailed to the user after a successful purchase. We have also added a link to our Moodle-based plugin for auto-enrolment.

    I sincerely, apologize for the delay in response. We redeveloped the plugin fora better user experience.

    Thank you.

    Wooo, no worries, will try the new update now, Thanks

    @ryscript
    Thanks! We will be eager to know your feedback.

    Also, please keep in mind that:

    After the users receive the order-complete email, they need to click the link of the course or courses that they bought (Please click this link

    It will then create and enroll the users in their courses.

    They can then access the courses using the username and password sent via email.

    Thank you.

    • This reply was modified 4 years, 9 months ago by Down Town.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Inconsistency Information and Bug’ is closed to new replies.