• Resolved Gautam Garg

    (@gautammkgarg)


    Hello Team

    I have raised this ticket at Github also
    https://github.com/themeum/tutor/issues/2045

    Thanks for providing the Payment Gateway Integration documentation on the website to help developers creating customer payment gateways with the ease.
    https://docs.themeum.com/tutor-lms/developer-documentation/custom-payment-gateways/step-1/

    I would like to report this issue in the code which is restricting the development of custom payment gateways. This line of code is forcing the developers to name the plugin in format “tutor-gatewayname/tutor-gatewayname.php“. This can’t be always true. As per policy of ww.wp.xz.cn, many times developers have to choose different slug. setting up this slug is not always possible. This is even stopping the demo code available at the link above to work, as plugin name for the demo code is “custompayment/custompayment.php
    https://github.com/themeum/tutor/blob/d96166965de2b706bc6b68ef830c69e3b83a86c7/includes/tutor-general-functions.php#L1503:L1504

    I request you to implement some other approach to check if the gateway is active or not. This approach gets failed many time.

    As per the policy of ww.wp.xz.cn, slug of third-party plugin can never be start from name/slug of other brands, “Tutor” in your case. So, developers will have to choose their custom slug names.

    In order to check if the plugin is active or not, you can try different ways like using defined function.

Viewing 4 replies - 1 through 4 (of 4 total)
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Issue in code restricting custom payment gateways’ is closed to new replies.