You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the issue arises because the payment_gateway field in the Payment Gateway Account DocType in ERPNext conflicts with the same field in LMS Settings. When I changed the field name payment_gateway in the LMS Settings DocType within the LMS app, the issue was resolved.
After changing the field, I noticed that the error 'Payment Gateway could not be found' still appeared, indicating that the system expects it to be a valid entry from the Payment Gateway DocType. This suggests that the field should be a Link field instead of a plain text field.
Given this, what would be the right approach to resolving the issue?
@sharif-dotcom, it seems like you are trying to use DPO as the payment gateway. Frappe Learning has been integrated with the Payments app to handle all payments. And the Payments app by default doesn't support DPO. You will have to contribute this to the app. https://github.com/frappe/payments
@pateljannat, that should be the goooo nowwwww. But then in the LMS Settings, the field for payment gateway, on payment settings tab should visually be a link field because thats what it reflects instead of being a data type
Describe the bug
Found our that on the LMS Settings (payment settings tab )the payment gateway field changes to a link field type on usage
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Was expecting to set a value for the data field instead that of the linked one
Screenshots
![Image](https://private-user-images.githubusercontent.com/120332756/407318861-632e8e15-e239-41c8-8a08-fc105f621330.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjYzOTMsIm5iZiI6MTczOTI2NjA5MywicGF0aCI6Ii8xMjAzMzI3NTYvNDA3MzE4ODYxLTYzMmU4ZTE1LWUyMzktNDFjOC04YTA4LWZjMTA1ZjYyMTMzMC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMVQwOTI4MTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02ZTZjNWZjYWQ2Zjc1Mzk0MDNkNTFiODI3MDMzYjVkN2U0ZGQwYWZjZjc5ZTY1OTMzYTkyNTRhNTg3ZmEwMjIwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.xVoMFGUOGGFvnvVx9vM10YaytVTemRr8sMQB1ZJxVW0)
A screenshot of a LMS Setting (doc) showing a field to be (data)
And to what it reflects on setting up the payment gateway on the payment settings tab
Desktop (Device and platforms ):
The text was updated successfully, but these errors were encountered: