After #87 and #480, we might run into more cases where people upgrade Backdrop to newer versions that have included contrib modules in core but leave the respective old contrib module folders in their /modules directory. Now, we already have tried to make sure that these left-over modules are not called, but we can never be really sure of what issues might be caused by leaving duplicate modules both in core and contrib module directories. Can we put some message/warning in place that "nags" people telling them that it is safe and recommended to remove the module folders from /module directory?
GitHub Issue #:
915
Recent comments
@caramia4457 Where I will set this "set “Test” mode" there is no option in the form. There is two option for live mode credentials and test mode credentials, so i only added the test mode...
Getting Error after submitting event register form By using Stripe Payment Processor
Hi geoma Welcome to Backdrop. Thank you posting detailed screenshots. As your field is an entity reference field, go into the field settings for field_insta_comuna and scroll to the...
Can't filter content in a View
Sounds like the Stripe processor isn’t fully initialising, so the extension tries to call create() on a missing Stripe client. On Backdrop/CiviCRM this usually happens when the payment processor...
Getting Error after submitting event register form By using Stripe Payment Processor